Problem with glibc update

[Steven Stern]

Following the note in Fedora-Announce, I ran up2date to get the latest glibc.
Is this a real problem or just a need to wait for the rpmfind mirror to fully
catch up?



[root at ciscy root]# up2date -u -v

Fetching package list for channel: fedora-core-1...

Fetching
http://fedora.redhat.com/releases/fedora-core-1/headers/header.info...
########################################

Fetching package list for channel: updates-released...

Fetching http://rpmfind.net/linux/fedora/core/updates/1/headers/header.info...
########################################
#######################################
Fetching Obsoletes list for channel: fedora-core-1...

Fetching Obsoletes list for channel: updates-released...

Fetching rpm headers...
########################################

Name                                    Version        Rel     
----------------------------------------------------------
glibc                                   2.3.2          101.4
i686  
No advisory information available



Testing package set / solving RPM inter-dependencies...
warning: package glibc = 2.3.2-101.4 was already added, replacing with glibc
<= 2.3.2-101.4
There was a package dependency problem. The message was:

Unresolvable chain of dependencies:
glibc-2.3.2-101.4                        requires glibc-common = 2.3.2-101.4



However, it looks I'm at a lower level

[root at ciscy root]# rpm -qa |grep glibc
glibc-2.3.2-101.1
glibc-kernheaders-2.4-8.36
glibc-common-2.3.2-101.1
glibc-headers-2.3.2-101.1
glibc-devel-2.3.2-101.1