Comment 1 for bug 1651286

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?