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

2019-06-12 Thread Guido G√ľnther
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 restarts the services
> - something like [1], I haven an MP up for that on salsa, might be
> slightly outdated
> 
> b) Specify both --no-stop-on-upgrade and --no-restart-after-upgrade
> Otherwise dh_installsystemd snippets will restart the service

That would mean three things for buster:

a) switch to dh12 (since we have that for newer versions since a while
   the change wouldn't be too bad)
b) add --no-stop-on-upgrade
c) Drop the sysv init scripts

While we could do the first two c) wouldn't be nice and we'd need to add
an explicit dependency on systemd-sysv. I'll try to get a round to test
this next week.

Cheers,
 -- Guido



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

2019-06-11 Thread Christian Ehrhardt
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 --no-stop-on-upgrade and --no-restart-after-upgrade
Otherwise dh_installsystemd snippets will restart the service

[1]: 
https://git.launchpad.net/~libvirt-maintainers/ubuntu/+source/libvirt/commit/?id=0b5b15b390903e5c282a8bb2c27d53d63e442f31

-- 
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd