On 21 December 2016 at 05:43, Steve Langasek <steve.langa...@canonical.com> wrote:
> This kind of removal does not normally require manual intervention by > the archive admins; proposed-migration should allow the package through > and the binary should then show up on the nbs report at > <http://people.canonical.com/~ubuntu-archive/nbs.html>. Since this old > version of libgolang-github-coreos-go-systemd1 is not in zesty-proposed, > and libgolang-github-coreos-go-systemd1 is not listed in debian/control > of the version of golang-github-coreos-go-systemd in zesty-proposed, I'm > at a loss to understand why this is stuck - but we should get to the > bottom of this rather than just manually removing the binary from zesty. > > Maybe something is automatically including libgolang-github-coreos-go- > systemd1 in the source or binary .changes, despite it not being listed > in debian/control? > Hm, I did a similar thing with the golang-github-coreos-pkg package and that went through proposed-migration fine (unless someone removed those binaries as well I guess). I wonder what the difference was. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1651286 Title: please remove libgolang-github-coreos-go-systemd1 from zesty To manage notifications about this bug go to: https://bugs.launchpad.net/britney/+bug/1651286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
