Re: Help! I upgraded ssh, it doesn't work, I want to go back to an earlier version.
Once upon a time, I heard Eric Hanchrow say Foolish me: I'd been happily running ssh 1:2.2.0p1 on my Potato system, and then I upgraded to ssh 1:2.2.0p1-1.1. (I got both of those versions from unstable.) Well, that newer version doesn't work on potato, because it requires a newer libc. I don't care to upgrade libc, and ssh is now brokenly installed, and will not start. What's the simplest way for me to get a working ssh 2.2.0 server again? I would *think* the easiest way would be to scare up another copy of the 1:2.2.0p1 package, but I don't know where to find it. I tried building the 1:2.2.0p1-1.1 package from source, on the assumption that the version that I built would not require a newer libc, but configure complained that it Could not find working SSLeay / OpenSSL libraries, please install. I couldn't figure out how to get past that point (yes, I tried installed OpenSSL). So: any suggestions for how I can get SSH working again? I'll build the binary myself, Set your deb-src to woody then do apt-get source -b ssh you might need libpam0g-dev, libssl095a-dev, and other to satisfy build dependency Chanop -- ,. | May Debian be with you ~~ [EMAIL PROTECTED]| `' pgpuq2sVFqCZc.pgp Description: PGP signature
Re: Help! I upgraded ssh, it doesn't work, I want to go back to an earlier version.
Foolish me: I'd been happily running ssh 1:2.2.0p1 on my Potato system, and then I upgraded to ssh 1:2.2.0p1-1.1. (I got both of those versions from unstable.) Well, that newer version doesn't work on potato, because it requires a newer libc. I don't care to upgrade libc, and ssh is now brokenly installed, and will not start. What's the simplest way for me to get a working ssh 2.2.0 server again? It doesn't *work* or it doesn't configure? You can force it to ignore any dependencies on the newer libc. It's worth a shot. It seems that many package maintainers set their requirements to whatever they had at the time they built that package because it would be a pain in the butt to actually check it against all of the older libc's. So, I've concluded that, when newer packages require a newer libc, it's sometimes a ruse. However, do NOT try to call their bluff if it's a critical package like ldso or something. Failing that, you can ftp to stable and get an older copy of ssh and force that to ignore dependencies on *older* libc's. Failing that dunno. But let me make a suggestion for the future: dpkg-repack. It makes a .deb file from any package that you've got on the system. This thing has SAVED MY ASS many, many, many times. What would be really cool is if it could let you specify a bunch of packages to automatically repack right before installing a new one. Know what I'm getting at here? So, I could tell repack that I want it to repack apache, apache-common, jserv, and ssh any time one of them is about to be upgraded or downgraded. So you'd always have fallback capability to the last working setup of them. Anyway good luck on ssh. - Joe
Re: Help! I upgraded ssh, it doesn't work, I want to go back to an earlier version.
On Wed, Oct 18, 2000 at 09:42:55PM -0700, Eric Hanchrow wrote: Foolish me: I'd been happily running ssh 1:2.2.0p1 on my Potato system, and then I upgraded to ssh 1:2.2.0p1-1.1. (I got both of those versions from unstable.) Well, that newer version doesn't work on potato, because it requires a newer libc. I don't care to upgrade libc, and ssh is now brokenly installed, and will not start. What's the simplest way for me to get a working ssh 2.2.0 server again? Why not dpkg --purge ssh then look in /var/cache/apt/archives/ for the older .deb then dpkg --install olddebfile.deb
