[lug] Weird glibc upgrade problem

[D. Stimits]

Justin wrote:
> 
> This is basically in response to everyone that replied to this original
> post. I was actually wondering how exactly other programs relied on
> glibc. Now I know, and obviously explains why most everything was
> broken. I know you're are supposed to use the upgrade procedure when
> using rpm but we did try that originally. All that kept happening was a
> bunch of dependency errors and we could never get it to go thru
> correctly. That is was brought up the idea of removing then re-
> installing glibc (obviously a bad idea). I had problems upgrading the
> glibc on one of my redhat boxes a while back too. I did use the upgrade
> flags but it still complained about dependencies, eventually I got it
> to work but it was such a pain. I just don't get how redhat can put up
> these upgrades to packages and just say rpm -Uvh them and you're all
> set. I rarely am able to do just that without any catches or problems
> that have to be worked out. Maybe I'm just not doing something right
> but rpm's have always given me trouble...
> 
> Thanks for all the input,
> 
> Justin
> 

rpm's have been a problem for several people. If it is possible to
upgrade some other package to get dependencies in line, then that is
often the route to choose. But if something isn't quite right and it is
giving you trouble, you might also consider these options:
--force
--nodeps

D. Stimits, stimits at idcomm.com