rpm reports 2 glibc, what can I do?

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


----- Original Message ----- 
From: "Neal Becker" <ndbecker2 at verizon.net>
To: <fedora-test-list at redhat.com>
Sent: Saturday, April 17, 2004 6:57 PM
Subject: Re: rpm reports 2 glibc, what can I do?


> Gene C. wrote:
>
> > On Saturday 17 April 2004 17: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?
> >
> > First, are you on an AMD64 system?  If you are, you are suppose to have
> > two ... one is i386 (actually i686) and the other is x86_64.
> >
> > Try "rpm -qi glibc"  ... this might give you additional info.
>
> Oh, I AM on x86_64.  I guess this is not why yum won't upgrade.
>
> rpm -qi glibc doesn't actually tell the arch, unless I'm blind.
>
> I guess this is useful:
> rpm --query --queryformat "%{ARCH}\n" glibc
> i686
> x86_64
>
> I'm really stuck trying to debug this.  I think I need to find something
> that can dump the format used by yum headers to see why it's confused.
> In /var/cache/yum I have
> glibc-0-2.3.3-20.x86_64.hdr
>
> and all other glibc-stuff all with same versions, all x86_64 versions
> present.  I tried rm /var/cache/yum and redownloading everything.  I tried
> different mirrors.  This problem has persisted - it's not due to mirror
> sync.

/etc/cron.daily/rpm outputs this nightly into /var/log/rpmpkgs. Enjoy.





More information about the fedora-test-list mailing list