On Fri, Aug 10, 2018 at 7:42 AM Michael Biebl <bi...@debian.org> wrote:
> Am 10.08.2018 um 13:32 schrieb Christian Ehrhardt:
> > I think I'd want/need a "dh_systemd_start
> > option to intentionally have it generate "just" for libvirt.service and
> > the sockets it depends on.
> > As mentioned, for all of the complexity pulling in the systemd people
> > help as well.
> > So I'm eager to see what they will reply here as well.
> I guess the complication arises from the fact that
> dh_installinit/invoke-rc.d directly handles systemd service files if the
> SysV init script and service file name match.
> dh_installsystemd only handles those unit files for which no
> corresponding SysV init script exists.
> I think the solutions for this could be, to let dh_installsystemd handle
> all systemd unit files.
> dh_installinit/invoke-rc.d on the other hand would be updated to only
> handle SysV init scripts.
> In the long run I guess this will be less confusing at is clearer which
> tool is responsible for which task and it makes it easier to override
> the behaviour in debian/rules.
> Felipe has been doing some initial work for enable that kind of
> behaviour at
This should help, but then you get the next problem: dh_installsystemd
parses the Also= lines, and generates deb-systemd-invoke for all referenced
I think the Also= lines in libvirtd.service are superfluous and removing
them should avoid this problem.
I'm still not sure why we parse Also= for starting. Michael, do you
remember the rationale?