> FYI: instructions from the the designers of the *-dbgsym system were that the > only thing > source packages do is drop old *-dbg binary packages from d/control files. > debhelper > compat level 9+ automation does the upgrade logic. The instructions also > stated that > maintainers must not attempt any manual dependency or Conflict tricks. Is > there > something radically different for Ubuntu?
I don't think it's that different in Ubuntu, but maybe britney is called/used a bit differently. What happened in the Ubuntu transition from -proposed to release was that squid-dbg-3.x (from squid3 src) had nowhere to upgrade to because the new debug package is called squid- dbgsym. Since the dbg package requires the exact squid-3.x package to be installed, it was holding the upgrade to squid-4. It was sorted out by an archive admin by deleting squid-dbg (from squid3 src). What I should have done is prepared a temporary squid3 (src) upload that didn't produce squid-dbg. squid-dbg would then become an NBS (https://wiki.ubuntu.com/UbuntuDevelopment/NBS), be removed (not sure if automatically), and then the squid-4 migration would have happened automatically. Using dh_strip's --dbgsym-migrate would probably not have helped, since a) that adds breaks/replaces to *all* dbgsym packages, not just the one replacing squid-dbg; and b) the dbgsym packages are in another repository, which I'm not sure britney considers. This attempt is what I meant with "a new upload will happen", but it wasn't necessary in the end. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780944 Title: Please provide Squid-4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1780944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
