In general Debian wants to support non-systemd systems more than we do - so dropping sysV might not only be an issue due to the systemd based start pulling off a restart of virtlogd - but also that this might be a derive that is more than we want.
So I was testing "with" sysV scripts again, which step exactly will trigger the initial issue which was: - something starts virtlogd - virtlogd realizes it has a new dependency (the admin socket) - the socket can't start as the service is up - virtlogd considers itself UP-But-Returns RC=1 - install breaks I want to make sure the steps there are really understood, and maybe "just" dropping the virtlogd sysV will be the middle path that makes it work. Will be back after a debug session of the exact step that triggers the initial issue ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786179 Title: double virtlogd sockets with services running can trigger issues on upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1786179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
