My apologies.
This was my fault.  I got glibc-debug mixed up with glibc-debuginfo and 
put it into the 'debuginfo' area.
I have uploaded it into the errata area.

Troy Dawson

Troy Dawson wrote:
> Hi Alex,
> The problem isn't that you already have those rpm's, it's the other way 
> around.
> Yum want's to update glibc, and glibc-devel, but it can't because 
> glibc-debug wants those exact versions of glibc.  Since glibc-debug 
> isn't in the errata area, it isn't going to be able to update along with 
> everything else.
> You are going to have to get the glibc-debug from the same place you got 
> it before, and update it along with the glibc's.  Or, if you are not 
> using glibc-debug, you could remove it.
> Troy
> 
> Alex Finch wrote:
> 
>>  We are getting these failure on the nightly yum update (SL 3.04):
>>
>>  --------------------
>>  YUM - errata
>>  --------------------
>> Unable to satisfy dependencies
>> Package glibc-debug needs glibc-devel = 2.3.2-95.30, this is not 
>> available.
>> Package glibc-debug needs glibc = 2.3.2-95.30, this is not available.
>>
>>
>> But so far as I can see we already have those rpms installed:
>>
>>  rpm -qa | grep glibc
>>
>> glibc-2.3.2-95.30
>> glibc-profile-2.3.2-95.30
>> glibc-headers-2.3.2-95.30
>> glibc-devel-2.3.2-95.30
>> glibc-utils-2.3.2-95.30
>> glibc-kernheaders-2.4-8.34.1
>> compat-glibc-7.x-2.2.4.32.6
>> glibc-common-2.3.2-95.30
>> glibc-debug-2.3.2-95.30
>>
>>  what goes on?
> 
> 
> 


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