Starting vlockd.service did allow the affected libvirt-packages to be updated: -8<------------------------------------ systemctl start virtlockd.service && aptitude safe-upgrade The following partially installed packages will be configured: libvirt-bin libvirt-daemon-system No packages will be installed, upgraded, or removed. 0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B of archives. After unpacking 0 B will be used. Setting up libvirt-daemon-system (1.2.7-10+b1) ... Setting up libvirt-bin (1.2.7-10+b1) ...
-8<------------------------------------ The original issue seems to apply to the current version of libvirt-daemon-system: -8<------------------------------------ systemctl stop virtlockd.service && dpkg-reconfigure libvirt-daemon-system Warning: Stopping virtlockd.service, but it can still be activated by: virtlockd.socket Job for virtlockd.service failed. See 'systemctl status virtlockd.service' and 'journalctl -xn' for details. Aug 23 13:04:51 osmium systemd[1]: Stopping Virtual machine lock manager... -- Subject: Unit virtlockd.service has begun shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit virtlockd.service has begun shutting down. Aug 23 13:04:51 osmium systemd[1]: Stopped Virtual machine lock manager. -- Subject: Unit virtlockd.service has finished shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit virtlockd.service has finished shutting down. Aug 23 13:04:52 osmium systemd[1]: Unit virtlockd.service cannot be reloaded because it is inactive. -8<------------------------------------ Regards, Linus -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
