[Yum] Security update/glibc name change seems to have confused yum

James Antill james-yum at and.org
Wed Jun 22 19:27:35 UTC 2011

John Reiser <jreiser at bitwagon.com> writes:

> On 06/22/2011 08:28 AM, James Antill wrote:
>>> ---> Package glibc-devel.x86_64 0:2.12-1.7.el6 set to be updated
>>> --> Processing Dependency: glibc = 2.12-1.7.el6 for package:
>>> glibc-devel-2.12-1.7.el6.x86_64
>>  And this is the latest version available, which is older than the one
>> you have installed ... so yum tries to solve the problem by installing
>> the .i686 version ... but that doesn't work out.
> How could that ever work (installing .i686 to fix a .x86_64 dependency,
> in this case "... for package: glibc-devel-2.12-1.7.el6.x86_64")?
> I've been bitten by this problem a number of times.  Why should yum
> even consider this?

 As Seth said, yum is just doing what it was told it could. As a good
example of this, if foo.i386 required bash ... you wouldn't want it to
actually require bash.i386.

 Saying that with RHEL-6.1 yum now also has a protected_multilib
configuration, and if that is on (default) it refuses to do things
like this (have foo.i386 and foo.x86_64 at different versions).

James Antill -- james at and.org

More information about the Yum mailing list