Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
I wanted to install the openssh deamon, so I would be able to ssh from home in to my office pc.
First I got stuck in the rpm dependency loop.
After the initial screwing around I got to the base of the problem(so I thought), which was the libc.so.6 package.
This comes with the glibc package. So I decided to install glibc 2.2.5 -34.
Now after about 5 different dependency problems the next one came, I needed the glibc-common-2.2.5-34 package.
Now at this point the redhat inc. server decided it was enough and quit on me by giving a proxy error and a lame excuse
that they experienced technical difficulties. So I went to www.rpmfind.net and downloaded the glibc-common-2.2.5-34 package.
I was really happy because I thought that this time I could pull it off and install this sucker, poor delusional kid you must think.
So I sat there behind my pc typing away the rpm -i commands when as a final kick to the head it gave me this dependency problem:
*************************************************************************************
error: Failed dependencies:
rpmlib (PartialHardlinkSets) <= 4.0.4-1 is needed by glibc-common-2.2.5-34
glibc < 2.2.5 conflicts with glibc-common-2.2.5-34
*************************************************************************************
I searched my ass off for this rpmlib, but it is no where to be found.
What the f--- is it and what can I do about it, or should I just bow down and accept that I will never be able to install this piece of software.
Sometimes I really think that this box is making stuff up as it goes along just to bug me.

Welcome to rpm hell. This is the reason why I strongly dislike any rpm based distro.
In case you don't know, glibc is the main c library on the system. Virtually all programs use it. There are a few incompatibilities between different glibc versions, and generally you should never just replace (upgrade) the glibc you're using. The results of doing this may be unpredictable. Not only for already installed programs, but also for newly installed ones, due to rpm dep problems.
My suggestion would be to do one of three things: 1) Find an rpm of openssh that is compiled against the same glibc version you have. 2) Install the openssh rpm you have, ignoring the dependencies. There's a good chance it will work even though the glibc version isn't 100% correct. 3) Compile and install openssh from source.

There is a package out there that will change rpms to tgz so you don't have to worry about all that stuff. I can't tell you where to find it because all I know is that it comes with Slackware 8.1 and I like it.
rpm2tgz
or maybe rpmtools

Why not download the source and build from
it!!! I download sshd version 1.2.5 to
replace an older version which has a security
hole, according to their website... It's
working just fine on my RedHat Linux 7.2.
Sometimes, it's better to do a little more
work so that you don't have to pull your
hair out!Lawrence

when installing from source the negative aspect is that you have no overlookable version controlling and upgrading system.

![]() |
Re: Important
|
Mandrake Red Hat Dual Boo...
|

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |