On Wed, Aug 8, 2012 at 5:11 PM, Martin Gracik <mgracik@xxxxxxxxxx> wrote:
> Hi,
>
> when I look at your code, it does not seem that the yum.conf you posted is created by that code
>
> # add the main repository
> section = "lorax-repo"
> data = {"name": "lorax repo",
> "#baseurl": repositories[0],
> "mirrorlist": mirrors[0],
> "enabled": 1}
>
> I don't see how this would create a yum.conf like this
>
> [lorax-repo]
> enabled = 1
> name = lorax repo
> baseurl =
> http://download.fedoraproject.org/releases/17/Everything/x86_64/os
>
> The yum.conf looks like it was created by the /sbin/lorax code...
>
> Before writing out the yumconf on line 123, you could print out the ConfigParser, to see if you get what you want.
Adding this immediately after writing:
with open(yumconf,'r') as f:
print f.read()
Prints:
[main]
tsflags = nodocs
reposdir =
keepcache = 0
cachedir = /tmp/lorax.TTFmmv/yum/yum.cache
plugins = 0
gpgcheck = 0
[lorax-repo]
enabled = 1
name = lorax repo
baseurl = http://download.fedoraproject.org/releases/17/Everything/i386/os
Does this look like the code is progressing alright?
Thanks,
Amit
>
>
>
> ----- Original Message -----
>> Hi,
>>
>> Ran into a bit of a issue with lorax for creating Boot ISO. This
>> command line works perfectly:
>>
>> # lorax -p fedora -v 1 -r 17 -s
>> http://download.fedoraproject.org/pub/fedora/linux/releases/17/Everything/x86_64/os
>> /tmp/lorax_op1
>>
>> Next, as part of a project, I am making using 'pylorax' and I am
>> creating a YumBase object and subsequently calling lorax.run() from
>> pylorax [1] . Now, currently this code creates a yum.conf like this:
>>
>> [main]
>> tsflags = nodocs
>> reposdir =
>> keepcache = 0
>> cachedir = /tmp/lorax.P1PBiz/yum/yum.cache
>> plugins = 0
>> gpgcheck = 0
>>
>> [lorax-repo]
>> enabled = 1
>> name = lorax repo
>> baseurl =
>> http://download.fedoraproject.org/releases/17/Everything/x86_64/os
>>
>> And the boot ISO creation fails with "lorax-repo: No more mirrors to
>> try" error. I am not quite able to understand what is going wrong
>> here in the latter case. Is it enough to just check the correctness
>> of
>> the yum.conf, or is there somewhere else I might be going wrong?
>>
>>
>> [1]
>> https://github.com/amitsaha/gsoc2012_fbs/blob/master/image_builder/bootiso.py
>>
>> PS: To add to the confusion, the same code builds a Boot ISO
>> perfectly
>> fine on one of my F17 installations, but fails on the others.
>>
>> Thanks a lot for any insights.
>>
>> -Amit
>>
>> --
>> http://echorand.me
>>
>> _______________________________________________
>> Anaconda-devel-list mailing list
>> Anaconda-devel-list@xxxxxxxxxx
>> https://www.redhat.com/mailman/listinfo/anaconda-devel-list
>>
>
> _______________________________________________
> Anaconda-devel-list mailing list
> Anaconda-devel-list@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/anaconda-devel-list
--
http://echorand.me
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
