Closing the lxc task as the lxc postinst doesn't suffer from this bug.
In lxc we have: remove) rm -f /etc/dnsmasq.d/lxc 2>/dev/null || true
# Try to restart a potential system wide dnsmasq invoke-rc.d dnsmasq restart 2>/dev/null || true ;;
Whereas in libvirt we have: remove|upgrade|failed-upgrade|abort-install|abort-upgrade|disappear) rm -f /etc/dnsmasq.d/libvirt-bin 2>/dev/null || true
Note that in libvirt's case, the file will be removed in all cases, whereas in lxc (and network-manager) we only do the removal on remove.
Closing the lxc task as the lxc postinst doesn't suffer from this bug.
In lxc we have:
remove)
rm -f /etc/dnsmasq.d/lxc 2>/dev/null || true
# Try to restart a potential system wide dnsmasq
invoke-rc.d dnsmasq restart 2>/dev/null || true
;;
Whereas in libvirt we have: upgrade| failed- upgrade| abort-install| abort-upgrade| disappear) d/libvirt- bin 2>/dev/null || true
remove|
rm -f /etc/dnsmasq.
# Try to restart a potential system wide dnsmasq
invoke-rc.d dnsmasq restart 2>/dev/null || true
;;
Note that in libvirt's case, the file will be removed in all cases, whereas in lxc (and network-manager) we only do the removal on remove.