Bug#905772: For me it needs sysV drop and --no-stop-on-upgrade and --no-restart-after-upgrade

On Tue, 11 Jun 2019 21:05:43 +0200 Christian Ehrhardt wrote: Testing now confirmed, that for the version in experimental I need to do both: a) drop the sysV - as Ubuntu has done for a while - without the sysV to systemd mapping still restarts the services - something like [1], I haven an MP up

Bug#905772: For me it needs sysV drop and --no-stop-on-upgrade and --no-restart-after-upgrade

Hi, Thanks for a lot for testing this! On Tue, Jun 11, 2019 at 09:05:43PM +0200, Christian Ehrhardt wrote: > Testing now confirmed, that for the version in experimental I need to do both: > > a) drop the sysV > - as Ubuntu has done for a while > - without the sysV to systemd mapping still

Bug#905772: For me it needs sysV drop and --no-stop-on-upgrade and --no-restart-after-upgrade

Testing now confirmed, that for the version in experimental I need to do both: a) drop the sysV - as Ubuntu has done for a while - without the sysV to systemd mapping still restarts the services - something like [1], I haven an MP up for that on salsa, might be slightly outdated b) Specify both