Existing rules that seemed to not fully work in the past related to our reports:
  # on Steve and paelzers system
  mv_conffile /etc/default/libvirt-bin /etc/default/libvirtd 1.3.3-2 
libvirt-bin   
  mv_conffile /etc/init.d/libvirt-bin /etc/init.d/libvirtd 1.3.3-2 libvirt-bin
  # on Steves system
  rm_conffile /etc/apparmor.d/libvirt/TEMPLATE 1.3.3-2 libvirt-bin              
   
  rm_conffile /etc/apparmor.d/libvirt/TEMPLATE 1.2.7-5~ libvirt-daemon-system
  rm_conffile /etc/apparmor.d/libvirtd/TEMPLATE 1.2.7-5~ libvirt-bin            
   
  rm_conffile /etc/apparmor.d/libvirtd/TEMPLATE 1.2.7-5~ libvirt-daemon-system

Now neither of our systems can be considered the cleanest systems ever
so I'll work on and attach a clean repro next.

Theories to debug: 
- Maybe because libvirt-bin was a transitional package and "has no maintainter 
scripts"?
- In the squid patch linked above it is suggested that dpkg-maintscript-helper 
has certain constraints on package owning/existing to trigger
- ...

-- 
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
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to