Re: No ssh service after upgrade from trixie Sid to forky Sid
Hi,
i quoted:
> > https://www.debian.org/releases/lenny/amd64/release-notes.en.txt
> > "Please note that using apt-get is not recommended for the upgrade
> > from etch to lenny."
Greg Wooledge wrote:
> That's VERY old.
Yeah. We all were much younger back then.
> The algorithms used by apt-get were improved after
> that point, and apt-get became the recommended tool for release
> upgrades. The recommendation has now switched to apt, though I'm
> not convinced there's any significant difference between apt-get and
> apt at this point other than the cosmetics and the automatic .deb
> file removal.
I wonder why
apt full-upgrade
does not perform the step
apt upgrade --without-new-pkgs
automatically.
I understand from its man page that it is mainly a frontend for some
specialized "apt-*" commands which reserves the freedom to do things
without having to stay backwards compatible with old use cases.
Whatever, the problems which i encountered with my Sid were due to
9 years of cruft and a little hack to keep old stuff running a few
years ago.
(I still have an old hard disk with Lenny. Possibly i could get it
to boot. But it would not be able to do remote shell with Trixie.)
Have a nice day :)
Thomas
Reply to: