Yep, that installed a conffile: $ dpkg-deb -e /home/mwhudson/Downloads/juju-core_2.0-beta1-0ubuntu1-16.04.1-juju1_amd64.deb $ cat DEBIAN/conffiles /etc/bash_completion.d/juju-core
Will need a maintainer script to clean that up. You could use rm_conffile, but as I think these files were only installed by PPA versions of the package, not anything from the archive (?) and more certainly we don't care at all about any local modifications the user may have made (i.e. it probably should never have been a conffile), I think just unconditionally deleting it in postinst might make most sense. On 21 July 2016 at 09:45, Martin Packman <martin.pack...@canonical.com> wrote: > Thinking about it, CI debs of that vintage should do, eg: > > <http://reports.vapour.ws/releases/3600/binaries> > > Can try installing on of those in a fresh vm then installing new > packaging over the top. > > -- > You received this bug notification because you are subscribed to juju- > core. > Matching subscriptions: juju packaging, juju-core packaging > https://bugs.launchpad.net/bugs/1600257 > > Title: > Broken bash completion with old ppa packages present > > To manage notifications about this bug go to: > https://bugs.launchpad.net/juju-core/+bug/1600257/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1600257 Title: Broken bash completion with old ppa packages present To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1600257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
