YUM update conflicts: 'glibc' and 'glibc-common' (F11, x86_64)
Kevin J. Cummings
cummings at kjchome.homeip.net
Sat Aug 22 20:55:05 UTC 2009
On 08/22/2009 04:00 PM, Ryan Lynch wrote:
> On Sat, Aug 22, 2009 at 15:44, Kevin J. Cummings
> <cummings at kjchome.homeip.net <mailto:cummings at kjchome.homeip.net>> wrote:
>
> On 08/22/2009 03:39 PM, Geoffrey Leach wrote:
> > On 08/22/2009 12:24:08 PM, Kevin J. Cummings wrote:
> >> On 08/22/2009 03:17 PM, Ryan Lynch wrote:
> >>> Running 'yum update' from the command line, I am getting some file
> >>> conflicts between different arch/versions of the 'glibc' and
> >>> 'glibc-common' packages. This machine runs F11-x86_64.
> >>>
> >>> Here's the actual error output:
> >>>
> >>> <code>
> >>> Transaction Check Error:
> >>> file /usr/share/doc/glibc-2.10.1/NEWS from install of
> >>> glibc-2.10.1-4.i686 conflicts with file from package
> >> glibc-2.10.1-2.x86_64
> >>> file /usr/bin/ldd from install of glibc-common-2.10.1-4.i586
> >> conflicts
> >>> with file from package glibc-common-2.10.1-2.x86_64
> >>> file /usr/lib/locale/locale-archive.tmpl from install of
> >>> glibc-common-2.10.1-4.i586 conflicts with file from package
> >>> glibc-common-2.10.1-2.x86_64
> >>> file /usr/share/doc/glibc-common-2.10.1/ChangeLog.bz2 from
> >> install
> >> of
> >>> glibc-common-2.10.1-4.i586 conflicts with file from package
> >>> glibc-common-2.10.1-2.x86_64
> >>> file /usr/share/i18n/locales/de_AT from install of
> >>> glibc-common-2.10.1-4.i586 conflicts with file from package
> >>> glibc-common-2.10.1-2.x86_64
> >>> </code>
> >>>
> >>> Is this a known issue, or did I screw something up?
> >>
> >> Something is screwed up. Possibly on your system. glibc-common.i586
> >> is
> >> conflicting with glibc-common.i686. I think you need one and not the
> >> other. Since you system is a base x86_64, I would suggest trying the
> >> following:
> >>
> >> # yum shell
> >>> remove glibc-common.i586
> >>> install glibc-common.i686
> >>> run
> >>
> >> and see if that helps....
> >
> > Hmmmm ... perhaps install glibc-common.x86_64? i686 is still 32 bit.
>
> Not if its a multi-lib problem. I assumed that the x86_64 part would
> straighten itself out.... But yes, he needs to ensure that all of his
> secondary libs are either all i586 or all i686 (where he has a choice
> between the two) and that they co-exist well with their x86_64
> counterparts (which should be the primary concern anyways).
>
>
>
> Here's the output of `yum list installed glibc-common glibc`, for reference:
>
> <code>
> Installed Packages
> glibc.i686 2.10.1-2 installed
> glibc.x86_64 2.10.1-2 installed
> glibc-common.x86_64 2.10.1-2 installed
> </code>
>
> I tried `yum remove glibc.i686`, but it wants to remove 116 packages,
> for dependencies. Mostly, it looks like stuff I installed while getting
> Skype for Linux to run, so I'm pretty sure its going to break some
> things if I remove it all.
Ryan,
You are barking up the wrong tree. Your problem is
glibc-common.i586. Something is trying to install this package and it
conflicts with your currently installed glibc-common.i686.
You need to track down where that dependency is coming from and deal
with it.
I find when dealing with wrong architecture RPMs, that using yum in
SHELL mode is much better then dealing with separate command lines as I
can do a remove *and* and install in one transaction and have better
control over it.
> Isn't this a packaging bug? There's no conflict between my
> currently-installed 'glibc.i686' and 'glib.x86_64' (2.10.1-2), although
> there is a conflict between the two archs' 'glibc-common' packages.
Possibly, but we need to know what is causing it first. i586/i686 are
not meant to be multilib (like x86_64/i686 is).
> -Ryan
>
--
Kevin J. Cummings
kjchome at rcn.com
cummings at kjchome.homeip.net
cummings at kjc386.framingham.ma.us
Registered Linux User #1232 (http://counter.li.org)
More information about the users
mailing list