No i386 images in rawhide,

[Panu Matilainen]

On Wed, 8 Apr 2009, James Laska wrote:

> On Wed, 2009-04-08 at 11:29 +0300, Panu Matilainen wrote:
>>> Basically the only thing on the box that's rawhide is glibc which is
>>> about where it got to before it barfed.
>>
>> Ahhah, this might be an all-important clue:
>> * Wed Apr  1 2009 Jakub Jelinek <jakub at redhat.com> 2.9.90-12
>> - update from trunk
>> - configure with --enable-experimental-malloc
>>
>> Note "experimental malloc", Apr 1st is the first known occurrence
>> of what appears to be memory corruption, and except for glibc, you
>> have
>> essentially F10 system exhibiting this issue. It's at least a rather
>> promising lead if nothing else.
>>
>>> If you contact me off list I can give you a login to the device to
>>> investigate if you like.
>>
>> Thanks, I might contact you later depending on where the trail
>> leads :)
>
> I didn't see a bug filed for this issue already.  I've filed the
> following bug to track this issue.
>
> Bug#494867 - "Rawhide i386 fails to boot - not syncing: No init found."
>
> It's currently assigned to the 'rpm' component, but I suspect that will
> change with further analysis.

FYI, it's glibc-2.9.90-12 i586-version that's broken, i686 version works 
just fine. And there's apparently a bug in yum that makes it pick i586 
over i686 on some situations. Thanks to Jesse Keating for hunting it down.

 	- Panu -