Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I upgraded my openssl version with the command:

rpm -i --nodeps openssl-0.9.8p-1.x86_64.rpm

And now I get following error for almost every command I enter:

/lib64/ version `GLIBC_2.7' not found (required by /lib64/ 

Will a simple update of GLIBC be enough? Like

rpm -i --nodeps glibc-2.9-2.9.x86_64.rpm

I'm kind of scared to try that because of the damage i've already caused.

share|improve this question

migrated from Oct 6 '11 at 7:14

This question came from our site for professional and enthusiast programmers.

Please help me...i'm on a customer system and am freaking out. thanks in advance – almightyBob Oct 5 '11 at 12:48
up vote 0 down vote accepted

Yeah, well, requiring --nodeps should be a big flashing sign that you're about to shoot yourself in the foot. Replacing core packages with some random rpm from the internet is unlikely to be successful, as you've noticed. Better luck next time, dude.

FWIW, you might be able to install the original openssl rpm by booting from a CD and playing with chroot.

Or, since Suse 10.3 isn't supported anymore anyway, you might as well update the entire system while you're at it.

share|improve this answer
yeah thats what i turned out doing. thanks for the heads-up. – almightyBob Oct 5 '11 at 14:13

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .