The .service files are a bit confusing -- pkg1.service has
Alias=pkg2.service and pkg2.service has Alias=pkg1.service. Thus you
have a unit with an alias which is actually a different unit, and then a
criss-cross aliasing. Normally Alias= should not point to an existing
different unit, these will
I can reproduce it with the package excerpts at
https://code.launchpad.net/~serge-hallyn/+git/pkg1
and
https://code.launchpad.net/~serge-hallyn/+git/pkg2
First
dpkg -i pkg1_1-1_amd64.deb
then
dpkg -i pkg1_1-2_amd64.deb pkg2_1-2_amd64.deb
On yakkety, this gives me:
(Reading
No, now I have reproduced it:
Adding user `libvirt-qemu' to group `libvirt-qemu' ...
Adding user libvirt-qemu to group libvirt-qemu
Done.
Failed to execute operation: No such file or directory
/usr/bin/deb-systemd-helper: error: systemctl preset failed on
libvirtd.service: No such file or
(so this probably should be marked invalid as cannot-be-reproduced, but
i'll leave it to a maintainer to do that in case this bug points to
something which still ought to be fixed)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hm, at this point this doesn't seem to be reproducing any more. Without
any changes to either init-system-helpers or libvirt. Only upgraded
packages are:
libpython3.5-minimal/yakkety 3.5.1-12 amd64 [upgradable from: 3.5.1-11]
libpython3.5-stdlib/yakkety 3.5.1-12 amd64 [upgradable from: