Thanks for reporting this Wayne.
It's fixed now with the newer i686 glibc and the repositories are built.
give it a try, and let me know if it works now for you.

Troy

Wayne Betts wrote:
> Sorry for the longwindedness here -- I'expect this must have been 
> noticed before, but I didn't turn it up in the archives so here goes...
> 
> I'm a bit concerned about the glibc packages in the bugfix repo for SL 305.
> There are two glibc packages in the bugfix repo (specifically 
> glibc-2.3.2-95.37.i686.rpm and glibc-2.3.2-95.39.i386.rpm) and I'd 
> hazard a guess that there are a lot of packages that depend on having a 
> glibc. (Note the differing version numbers. -- in the bugfix repo, all 
> the glibc-* packages are of the 2.3.2-95.39 variety except the 
> glibc-2.3.2-95.37.i686.rpm)  Consider the following system which is 
> configured to use the bugfix repo.  It finds the currently installed 
> i686 version, plus both the available updated i386 and i686 versions:
> 
> [root@staruser01 root]# rpm -q glibc
> glibc-2.3.2-95.33
> [root@staruser01 root]# uname -p
> i686
> [root@staruser01 root]# yum info glibc
> Gathering header information file(s) from server(s)
> Server: SL 305 bugfixes
> Server: SL 305 errata
> Server: SL 305 main
> Finding updated packages
> Downloading needed headers
> Looking in Available Packages:
> Name   : glibc
> Arch   : i686
> Version: 2.3.2
> Release: 95.37
> Size   : 11.80 MB
> Group  : System Environment/Libraries
> Repo   : SL 305 bugfixes
> Summary: The GNU libc libraries.
> <snip>
> 
> Name   : glibc
> Arch   : i386
> Version: 2.3.2
> Release: 95.39
> Size   : 7.62 MB
> Group  : System Environment/Libraries
> Repo   : SL 305 bugfixes
> Summary: The GNU libc libraries.
> <snip>
> 
> Looking in Installed Packages:
> Name   : glibc
> Arch   : i686
> Version: 2.3.2
> Release: 95.33
> Size   : 11.79 MB
> Group  : System Environment/Libraries
> Repo   : Locally Installed
> Summary: The GNU libc libraries.
> <snip>
> 
> If I ask to update glibc, it says the latest version is already 
> installed, though it doesn't seem to be from the output above:
> 
> [root@staruser01 root]# yum update glibc
> Gathering header information file(s) from server(s)
> Server: SL 305 bugfixes
> Server: SL 305 errata
> Server: SL 305 main
> Finding updated packages
> Downloading needed headers
> glibc is installed and the latest version.
> No actions to take
> 
> and if I do a yum update, it claims it will install glibc-2.3.2-95.39 to 
> satisfy dependencies:
> 
> [root@staruser01 root]# yum update
> Gathering header information file(s) from server(s)
> Server: SL 305 bugfixes
> Server: SL 305 errata
> Server: SL 305 main
> Finding updated packages
> Downloading needed headers
> Resolving dependencies
> .Dependencies resolved
> I will do the following:
> <snip>
> I will install/upgrade these to satisfy the dependencies:
> [deps: glibc 2.3.2-95.39.i386]
> Is this ok [y/N]:
> 
> Notice that here it is trying to install the i386 version, though I 
> think it really should be using the i686 version.  Apparently it is 
> trying to resolve a dependency in glibc-common (if nothing else) when it 
> comes up with this:
> 
> [root@staruser01 root]# yum update glibc-common
> Gathering header information file(s) from server(s)
> Server: SL 305 bugfixes
> Server: SL 305 errata
> Server: SL 305 main
> Finding updated packages
> Downloading needed headers
> Resolving dependencies
> .Dependencies resolved
> I will do the following:
> [update: glibc-common 2.3.2-95.39.i386]
> I will install/upgrade these to satisfy the dependencies:
> [deps: glibc 2.3.2-95.39.i386]
> Is this ok [y/N]: y
> Downloading Packages
> Getting glibc-2.3.2-95.39.i386.rpm
> glibc-2.3.2-95.39.i386.rp 100% |=========================| 3.3 MB    00:00
> Getting glibc-common-2.3.2-95.39.i386.rpm
> glibc-common-2.3.2-95.39. 100% |=========================|  12 MB    00:01
> Running test transaction:
> Test transaction complete, Success!
> glibc-common 100 % done 1/4
> glibc 100 % done 2/4
> Stopping sshd:[  OK  ]
> sleep: relocation error: /lib/i686/librt.so.1: symbol 
> __pthread_clock_settime, version GLIBC_PRIVATE not defined in file 
> libpthread.so.0 with link time reference
> Starting sshd:[  OK  ]
> Completing update for glibc  - 3/4
> Completing update for glibc-common  - 4/4
> Updated:  glibc-common 2.3.2-95.39.i386
> Dep Installed:  glibc 2.3.2-95.39.i386
> Transaction(s) Complete
> 
> Now, as it happens, I've said yes to this installation a few times 
> without much thought, and it has each time produced such error messages 
> as when restarting the sshd and various other tasks.  I believe also 
> that such an update broke a production system with most peculiar 
> symtpoms after just such an update.  I'm going to carefully test things, 
> but it would greatly ease my mind if someone could confirm that 
> something is wrong here.
> 
> I tried to fix the system manually, but can't satisfy dependencies:
> [root@staruser01 root]# rpm -Uvh --oldpackage glibc-2.3.2-95.37.i686.rpm
> error: Failed dependencies:
>        glibc-common = 2.3.2-95.37 is needed by glibc-2.3.2-95.37
> 
> Any help will be greatly appreciated.  Ideally a fix would roll itself 
> out in the next yum cron jobs, but since the bugfixes aren't applied in 
> the standard yum cron jobs, that might not help and I'll have to try to 
> recall the handful of systems I've manually updated with the bugfixes.
> 
> 
> Wayne


-- 
__________________________________________________
Troy Dawson  [log in to unmask]  (630)840-6468
Fermilab  ComputingDivision/CSS  CSI Group
__________________________________________________