please remove libgolang-github-coreos-go-systemd1 from zesty

[Michael Hudson-Doyle]

Hi,

lxd no longer depends on this package, so there is no longer any reason to build it as a shared library. I've uploaded (well synced) a new version of the package that does not build them but to get it to migrate AIUI libgolang-github-coreos-go-systemd1 must be removed from Zesty.

[Steve Langasek (vorlon)]

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?

[Steve Langasek (vorlon)]

This may be triggered by the move from a source that builds an arch: any package, to one that only builds an arch: all package.

I'd say that's a bug in proposed-migration, but not one that should block fixing this particular migration.

[Steve Langasek (vorlon)]

Removing packages from zesty:
 libgolang-github-coreos-go-systemd1 12-1ubuntu4 in zesty amd64
 libgolang-github-coreos-go-systemd1 12-1ubuntu4 in zesty arm64
 libgolang-github-coreos-go-systemd1 12-1ubuntu4 in zesty armhf
 libgolang-github-coreos-go-systemd1 12-1ubuntu4 in zesty i386
 libgolang-github-coreos-go-systemd1 12-1ubuntu4 in zesty powerpc
 libgolang-github-coreos-go-systemd1 12-1ubuntu4 in zesty ppc64el
 libgolang-github-coreos-go-systemd1 12-1ubuntu4 in zesty s390x
Comment: NBS
Remove [y|N]? y
7 packages successfully removed.

[Michael Hudson-Doyle (mwhudson)]

On 21 December 2016 at 05:43, Steve Langasek <email address hidden>
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.