rpm reports 2 glibc, what can I do?

Nico Kadel-Garcia nkadel at merl.com
Mon Apr 19 18:31:50 UTC 2004


----- Original Message ----- 
From: "Sean Bruno" <sean.bruno at dsl-only.net>
To: "For testers of Fedora Core development releases"
<fedora-test-list at redhat.com>
Sent: Saturday, April 17, 2004 5:53 PM
Subject: Re: rpm reports 2 glibc, what can I do?


> I am seeing the same thing this AM.  Open a Bugzilla if you please.  Or
> I can do it.
>
> On Sat, 2004-04-17 at 14:50, Neal Becker wrote:
> > I'm trying to debug this:
> >
> > yum update
> > .....Unable to satisfy dependencies
> > Package dbh-devel needs dbh = 1.0.18-1, this is not available.
> > Package samba needs samba-common = 0:3.0.2a, this is not available.
> > Package xorg-x11-libs needs xorg-x11-libs-data =
0.0.6.6-0.0.2004_03_11.9,
> > this                   is not available.
> > Package glibc needs glibc-common = 2.3.3-18, this is not available.
> >
> > I found this:
> > rpm -q glibc
> > glibc-2.3.3-18
> > glibc-2.3.3-18
> >
> > Probably this is the problem.  Obviously, I can't just erase glibc to
fix
> > it.  What can I do?

Do a "rpm -qa glibc -qf '%{name}-%{version}-%{release}.%{arch}.rpm'. You
probably have both the i386 and i686 or other architecture RPM installed.
The usual way to fix this is to select the *correct* format RPM, download
it, and do an "rpm -Uvvvh --replacepkgs glibc-2.3.3-18.i686.rpm" with the
RPM. You may also need to do an "rpm --rebuilddb" command to straighten out
any confusion about overlapping files.

This usually happens when people try updating such packages by hand and
don't realize there's a different one for each architecture.





More information about the fedora-test-list mailing list