On 2018-02-21 16:49 -0500, Greg Wooledge wrote:
> On Wed, Feb 21, 2018 at 10:39:15PM +0100, Sven Joachim wrote:
>> 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:
>
> Moot argument. You don't *DO* a direct upgrade from wheezy to stretch
> in the first place. You go wheezy->jessie, and then jessie->stretch.
Certainly. I only mentioned this because Jimmy had suggested the
reckless method of directly upgrading from Wheezy to Stretch, and I was
curious how badly it would break.
Cheers,
Sven
