On Wed, 2007-07-25 at 11:07 -0600, Phil Meyer wrote:
Phil Meyer wrote:
> Jesse Keating wrote:
>> On Tue, 24 Jul 2007 10:16:40 -0600
>> Phil Meyer <pmeyer(a)themeyerfarm.com> wrote:
>>
>>
>>> Sorry for the slow response. Had to finish Harry Potter. :)
>>>
>>> After verifying the yum is 3.2.2 all the way through, still no change.
>>>
>>
>> Can I hazard a guess that you're doing a media installation? (burned
>> iso, or qemu booting from the iso, or NFS iso dir)?
>>
>>
>> ------------------------------------------------------------------------
>>
>> --
>> Fedora-buildsys-list mailing list
>> Fedora-buildsys-list(a)redhat.com
>>
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
>
> Yes. I found this work around:
>
>
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=246357#c26
>
> Am testing that right now.
The workaround suggested in comment 26 works.
Basically, in the yum configuration file you are using to build, tell it
to ignore updates for yum and yum-updatesd. Like this:
[updates]
name=Fedora $releasever - $basearch - Released Updates
...
exclude=yum yum-updatesd
enabled=1
gpgcheck=1
It does not matter what version of yum is on the build server, just what
version is built into the CD/DVD image.
The new version of yum in updates-testing is 3.2.2 and does not resolve
the issue.
Further Observations:
In yum-3.2.0 on the CD/DVD image, both headers directories are created.
/tmp/cache/headers
/tmp/cahe/anaconda.../headers
The second of those is populated.
Good Luck!
Hi , we know the regression is between yum-3.2.0 and yum-3.2.1 , so
shouldn't be difficult , find and revert what make stop population of
headers . I simply don't had time to further investigation.
Someone write in this malling list that could be fix (the missing
headers) on anaconda what is the status of anaconda ?
thanks,
--
Sérgio M.B.