[NTLUG:Discuss] ssh

[Jay Cox]

On Thu, 21 Mar 2002, TJ Davis wrote:

>     I tried upgrading to the newest openssh but got failed dependencies left
> and right.  First it needed glibc.  Then glibc needed glibc-common.  Then
> glib-common needed something else.  After about the 6th dependency I gave up
> on installing all of the dependencies.  Anyways, this is a Redhat 7.0 box
> unfortunately which will be remedied during the summer (upgraded to 7.2) so
> that could have something to do with all of the failed dependencies.  Any
> suggestions on getting all of the dependencies in one package or something
> to that affect?  I have never had much luck with installing software when
> dependencies start failing.  Thanks for your help.

When it prompted you that glibc failed, that should prompt you to give up
on using that binary rpm.  Glibc is the library common to every program
written for linux (unless, perhaps, you are talking about the very few
programs written totally in assembly for linux).  I wouldn't be too
suprised if upgrading glibc might actually have broken a few programs (and
neither would I be suprised if it had not broken any).

If you fear going down the dependency upgrading path, you might consider
downloading/building a src.rpm and installing the resultant binary.  It
has all the advantages of building from source, plus I've found that a
source rpm will have a patchfile that might be necessary to compile
the source on a redhat machine (rpm will apply the patch for you).
This is a rule of thumb: some programs will just need newer librarys no
matter what you have to do to upgrade or install.

Jay Cox