Ubuntu
golang-github-coreos-go-systemd package

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

Bug #1651286 reported by Michael Hudson-Doyle
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
britney
New
Undecided
Unassigned
golang-github-coreos-go-systemd (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

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.

Revision history for this message
Steve Langasek (vorlon) 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?

Changed in golang-github-coreos-go-systemd (Ubuntu):
status: New → Incomplete
Revision history for this message
Steve Langasek (vorlon) wrote :

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.

Revision history for this message
Steve Langasek (vorlon) wrote :

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.

Changed in golang-github-coreos-go-systemd (Ubuntu):
status: Incomplete → Fix Released
Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote : Re: [Bug 1651286] Re: please remove libgolang-github-coreos-go-systemd1 from zesty

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.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.