[NTLUG:Discuss] Avoiding evil causes catch-22 when updating glibc on fresh RH62 box

[Cameron]

* richard at rain.lewisville.tx.us [2001.06.13 12:50]:
: OK.  I scratched the previous message I was going to send and got one step
: closer.   *BUT*
: 
: I am running into a  catch-22 situation trying to update GLIBC to 2.2.
: 
: Scenario.  Fresh custom install of RH 6.2.  No Gnome--console mode only.
: Server is currently running on one nic behind a masq box.
: 
: Packages installed or updated so far.
: 
: Webmin
: rpm4
: 
: one (of many) packages that I WANT to load but can't
: openssl-0.9.6a-4.i386.rpm
: 
: problem:  Failed dependencies:  libc.so.6(GLIBC_2.2) is needed by
: openssl.....
: 
: ok...no problem.  I download the new glibc rpms from redhat (
: RHSA-2001:002-03) into their own directory and tried to install them.  I
: tried the commands
: 
: rpm -Fvh *.rpm
: rpm -ivh *.rpm
: and even tried to do each one manually.
: 
: [catch22]
: glibc-2.2-12.i386.rpm won't install because glibc-common = 2.2 is needed by
: glibc-2.2-12 (along with various other packages like python, passwd, etc...)
: 
: glibc-common won't install because glibc version less that 2.2 conflicts.
: (WELL DUH!)
: [/catch22]
: 
: I've attempted a --force option on various command lines but I'm not getting
: through to this +near+ evil OS.
: 
: help!

My general rule of thumb is to *never* update glibc just because I want
to.  I only update glibc when there are security or bugfix packages that
come from my distro.  If you have the balls to update glibc by yourself,
then you should have no problem reinstalling everything when you foobar
your system.  ;-p  (Speaking from experience)

What you should do is get the SRPM for openssl and rebuild it yourself.
The glibc dependency is there because that's what openssl was built
with.  Get the source and you solve that problem.
-- 
cameron
/ Do not meddle in the affairs of sysadmins, \
\  for they are subtle and quick to anger.   /