yum update - Glibc Problem

[mailing-lists at hughesjr.com (Johnny Hughes)]

On Thu, 2005-11-17 at 18:21 +0000, Lee W wrote:
> Jim Perrin wrote:
> 
> >>Oh well, I'm trying an update with exactarch=0 to see if that works.
> >>Failing that I'll download the updated 4.2 ISO's and install from that.
> >>
> >>    
> >>
> >
> >Be careful with that. It may affect more than just glibc. If you're
> >going to do update with exactarch=0, do 'yum install glibc' or
> >something similar to avoid pulling in ALL other affected rpms.
> >
> >
> >
> >
> >
> >
> >
> >--
> >Jim Perrin
> >System Architect - UIT
> >Ft Gordon & US Army Signal Center
> >_______________________________________________
> >CentOS mailing list
> >CentOS@xxxxxxxxxx
> >http://lists.centos.org/mailman/listinfo/centos
> >  
> >
> It's not a live system, so if ends up broken I'm not bothered. 
> 
> Seeing as it seems that just the i386 arch is availabe, would it not be
> best to change all other packages to be i386 as well (which I figured
> doing yum update would do) to avoid this problem in the future if
> another package is updated?
> 

Lee,

You will want to just upgrade the glibc to i386 (it is really i486, but
that is another story).

All the other items that are i586 are OK, and should remain so.  And you
want to keep them.

If the glibc wasn't really i486 (which is a little more stable than i586
and as fast) then we would have modified the code to build the i586.

Thanks,
Johnny Hughes
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.centos.org/pipermail/centos/attachments/20051117/7b7fe509/attachment.bin