The rm_conffile was also working manually but not on the upgrade itself. So I was running with DPDK_DEBUG=1 for dpkg-maintscrip-helper in the real upgrades: Preparing to unpack .../libvirt-bin_2.5.0-3ubuntu5~cloud0_amd64.deb ... Unpacking libvirt-bin (2.5.0-3ubuntu5~cloud0) over (1.3.1-1ubuntu10.10) ... [...] Selecting previously unselected package libvirt-daemon-system. Preparing to unpack .../libvirt-daemon-system_2.5.0-3ubuntu5~cloud0_amd64.deb ... DEBUG: dpkg-maintscript-helper: Executing /usr/bin/dpkg-maintscript-helper mv_conffile in preinst of libvirt-daemon-system DEBUG: dpkg-maintscript-helper: CONFFILE=/etc/default/libvirt-bin -> /etc/default/libvirtd PACKAGE=libvirt-bin LASTVERSION=1.3.3-2 ACTION=install PARAM=
Look at the PARAM= argument. Since libvirt-daemon-system is new it has no old version. That is why all the commands fail on the real upgrade. That sounds more than ever like the squid change we had linked above, implementing that and adding the missed rm_conffiles for a test. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1694159 Title: Complete libvirt migration to Debian style packaging (dependencies, conffiles) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ginger/+bug/1694159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
