So finding a machine turns out a bit more complicated. Anyhow, I looked into the libvirt-bin binary package for ppc64le and weirdly it does also contain the /lib/systemd/system/virtlockd.[service,socket] files. So why is the init.d script being run? Also the virtlockd should be there /usr/sbin/virtlockd. Question is which way the scripts needs to be modified. Could be that PROCESS=virtlockd is ok but it needs to set and export a PATH environment which also contains /usr/sbin (like the virtlogd one does). I must admit I had to fix other issues (found by lintian) in that script which I copied from the upstream source tree. Just testing is a problem as on x86 with systemd and sysvinit files around the systemd variant always wins.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1547208 Title: package libvirt-bin=1.3.1-1ubuntu1 fails to install due to new virtlockd initd script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1547208/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
