[Pkg-libvirt-maintainers] Bug#905772: Trying to drop sysv is leading to other complexities

Christian Ehrhardt christian.ehrhardt at canonical.com
Thu Aug 9 14:57:13 BST 2018


Hi,
Just FYI simply removing the installation of the sysV scripts will uncover
other issues.
If sysV and systemd services are installed the former still are prefered.

So with libvirtd sysV gone it will pick up libvirtd.service
That will parse the Requires which contains virtlogd-socket  will
eventually lead to:
  deb-systemd-invoke $_dh_action 'libvirtd.service' 'virtlockd.socket'
'virtlogd.socket'

And that will stop the service to restart the socket.

I have taken a few more approcahes to this, like full conversion to
dh_isntallsystemd and others.
But all failed so far by still calling the command above which will
effectively restart virtlogd which is not what we want.

I start to consider things that look bad at first, for example keep the
libvirtd sysV script but make it almost empty.
At least the dependencies to the virtlogd sysV script have to go away -
otherwise it will block on that before the sysV to systemd wrapper kicks in
:-/

Hoping you have a better Idea how to resolve,
Christian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-libvirt-maintainers/attachments/20180809/e4794188/attachment.html>


More information about the Pkg-libvirt-maintainers mailing list