Hi,
I have a SuSE Enterprise 8 Server set up on an i586 platform. I had downloaded the rpms for GLIBC-2.3.2-6 from rpmfind and used YaST2 to install it. However, when I run rpm -qa | grep glibc , (I assume this is the correct command. I am learning the linux system and am not an expert by any means) to find the current version of glibc it returns the following:
glibc-i18ndata-2.2.5-163
glibc-2.2.5-164
glibc-locale-2.2.5-163

Although it appears that the new version of glibc installs OK (I don't receive an error, no dependancy issues), it apparently doesn't work right. Hence I cannot install other packages due to the version of glibc that is on my system.

Can anyone help me out with this issue?

Thanks,
Ken

go back to the default glibc and try an
rpm -Uvh glibc*

oh and try suse specific rpms..

Thanks ganja_guru,

The package i had downloaded from rpmfind was for SuSE Linux 8.2 for i386 (glibc-2.3.2-6.i586.rpm). The distro i am using (SuSE Linux enterprise server 8) is a fully functional evaluation version i got from Novell. However, there are no updates available from Suse or Novell for this. I am assuming that the file I got from rpmfind is appropriate.

Anyway, I ran the command you suggested and got the following error:
SUSE1:~ # rpm -Uvh glibc-2.3.2-6.i586.rpm
error: failed dependencies:
glibc = 2.2.5 is needed by lsb-runtime-1.2-37
glibc = 2.2.5 is needed by glibc-locale-2.2.5-163

I am going to see if these are someting I can upgrade also, then try again. Anything else I should be looking at?

Thanks,
ken

how abt rpm -Uvh --nodeps glib*

wait a sec...im not so sure suse linux enterprise 8 and suse 8.2 are the same thing.....

I was thinking the same thing. Is there anyway to determine the version other than from the lable on the install media?

I just set up another system (lucky we just took a bunch of machines out of service. They now become my personal lab ). I installed Fedora Core 2 and am able to do some of the installs that I want on that box. Still struggling with some dependency issues regarding upgrading samba from v3.0.3 v3.0.7, but its not imperative, and it gives me a problem to try to solve.

Thanks for all you help!