Re-installing `libvirt-daemon-system` is enough to trigger the issue.
This might be an effect of changed dh_compat handling in dh_installsystemd. I've found this difference: Hirsute: /var/lib/dpkg/info/libvirt-daemon-system.postinst: deb-systemd-invoke start 'libvirt-guests.service' 'virtlockd.service' 'virtlogd.service' >/dev/null || true /var/lib/dpkg/info/libvirt-daemon-system.postinst: deb-systemd-invoke start 'libvirtd-admin.socket' 'libvirtd-ro.socket' 'libvirtd.socket' 'virtlockd-admin.socket' 'virtlockd.socket' 'virtlogd-admin.socket' 'virtlogd.socket' >/dev/null || true Same libvirt code in Focal backports: /var/lib/dpkg/info/libvirt-daemon-system.postinst: deb-systemd-invoke $_dh_action 'libvirt-guests.service' 'virtlockd.service' 'virtlogd.service' >/dev/null || true /var/lib/dpkg/info/libvirt-daemon-system.postinst: deb-systemd-invoke $_dh_action 'libvirtd-admin.socket' 'libvirtd-ro.socket' 'libvirtd.socket' 'virtlockd-admin.socket' 'virtlockd.socket' 'virtlogd-admin.socket' 'virtlogd.socket' >/dev/null || true Please notice that in Hirsute it does only `start` various services (but never restarts) and only `start` the socket but never restarts them. In d/rules that looks like: dh_installsystemd -p libvirt-daemon-system --no-also --no-stop-on-upgrade $(LIBVIRT_SYSTEM_SERVICES) dh_installsystemd -p libvirt-daemon-system --no-also --no-stop-on-upgrade $(LIBVIRT_SOCKETS) Due to the backports we switch debhelper 13 to debhelper 12 (in Focal and bionic [which has v12 in backports]). That is the most likely source of this changed behavior. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944413 Title: upgrading libvirt restarts libvirt-guests.service (when using server- backports) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1944413/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
