We know that libvirtd can't be removed as it is early in the postrm and
at this time we know it will trigger:
$ delgroup libvirtd
/usr/sbin/delgroup: `libvirt-dnsmasq' still has `libvirtd' as their primary
group!
But removing it afterwards when it can be removed only ends up breaking
slightly different:
RET=20 Unsupported command "the" (full line was "The group `libvirtd'
does not exist.") received from confmodule.
Maybe the sysuser config of libvirtd makes debconf want to remove it,
but in the combination we have in place this fails and that makes it
fail badly. I need to track this down in more detail, but this week will
unlikely find time for it.
As a workaround for now, I found that removing/purging libvirt-daemon-
system once more passed fine so you can just re-run whatever you did to
trigger the purges and the second time it should pass.
** Changed in: libvirt (Ubuntu)
Status: Confirmed => Triaged
** Changed in: libvirt (Ubuntu)
Importance: Undecided => Medium
** Tags added: server-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951903
Title:
package libvirt-daemon-system 4.0.0-1ubuntu8.19 failed to
install/upgrade: installed libvirt-daemon-system package post-removal
script subprocess returned error exit status 128
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1951903/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
