On 2018-02-21 16:01 -0500, Greg Wooledge wrote:
> On Wed, Feb 21, 2018 at 12:58:11PM -0800, Jimmy Johnson wrote:
>> For all the "Na" Sayers here, nothing lost except for sometime and something
>> to gan the system you want and if you can't make it work format and do a new
>> system, but remember there is no "sysvinit" in Stretch.
>
> There is. It's just not the default.
Speaking of sysvinit, one problem with a direct upgrade from Wheezy to
Stretch is that there is no _package_ named sysvinit in Stretch, so you
will be left with the old sysvinit from Wheezy and have to do a manual
upgrade, e.g. like this:
# apt-get install sysvinit-core
# dpkg --purge --force-remove-essential sysvinit
Other than that, on a fairly minimal chroot this worked surprisingly
well. However, on a system with ~2000 packages I would rather not try
it. There are certainly many other cases where you will be left with
old packages without an obvious upgrade path, obsolete conffiles,
directories which should be symlinks or vice versa and other issues
which are not immediately obvious but may bite you many months later.
Cheers,
Sven
