Debian Bug report logs - #1082307
RM: golang-github-eapache-go-resiliency -- ROM; accidental duplicate

Display info messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Helmut Grohne <helmut@subdivi.de>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: golang-github-eapache-go-resiliency-dev,golang-gopkg-eapache-go-resiliency.v1-dev: aliasing conflict on /usr/share/gocode/src/github.com/eapache/go-resiliency

Date: Thu, 19 Sep 2024 21:39:40 +0200

Package: golang-github-eapache-go-resiliency-dev,golang-gopkg-eapache-go-resiliency.v1-dev
Severity: important

golang-github-eapache-go-resiliency-dev installs
/usr/share/gocode/src/github.com/eapache/go-resiliency as a directory
and installs files into it whereas
golang-gopkg-eapache-go-resiliency.v1-dev installs the same location as
a symbolic link. This is an aliasing conflict and what happens on the
filesystem depends on the unpack order. For instance, installing
golang-github-eapache-go-resiliency-dev, then installing
golang-gopkg-eapache-go-resiliency.v1-dev, then removing
golang-github-eapache-go-resiliency-dev results in
/usr/share/gocode/src/github.com/eapache/go-resiliency becoming an empty
directory and golang-gopkg-eapache-go-resiliency.v1-dev likely ceases to
work.

Please figure out which package should own
/usr/share/gocode/src/github.com/eapache/go-resiliency and reassign the
bug accordingly.

Helmut

Message #10 received at 1082307@bugs.debian.org (full text, mbox, reply):

From: Mathias Gibbens <gibmat@debian.org>

To: 1082307@bugs.debian.org

Subject: Re: golang-github-eapache-go-resiliency-dev: duplicate of golang-gopkg-eapache-go-resiliency.v1-dev

Date: Thu, 28 Nov 2024 22:12:28 +0000

[Message part 1 (text/plain, inline)]

Control: retitle -1 golang-github-eapache-go-resiliency-dev: duplicate of golang-gopkg-eapache-go-resiliency.v1-dev
Control: reassign -1 golang-github-eapache-go-resiliency-dev

  Oops, somehow I missed that go-resiliency had already been packaged.
I've updated the single rdep using golang-github-eapache-go-resiliency-
dev, and after the archive settles I will then update this bug to a RM
request.

Mathias

[signature.asc (application/pgp-signature, inline)]

Message #19 received at 1082307@bugs.debian.org (full text, mbox, reply):

From: Mathias Gibbens <gibmat@debian.org>

To: 1082307@bugs.debian.org

Subject: RM: golang-github-eapache-go-resiliency -- ROM; accidental duplicate

Date: Sat, 30 Nov 2024 22:23:42 +0000

[Message part 1 (text/plain, inline)]

Control: retitle -1 RM: golang-github-eapache-go-resiliency -- ROM; accidental duplicate
Control: reassign -1 ftp.debian.org
Control: severity -1 normal

  Please remove golang-github-eapache-go-resiliency. I packaged the
library not realizing it was already in the archive as golang-gopkg-
eapache-go-resiliency.v1.

  I have updated the single rdep of golang-github-eapache-go-
resiliency-dev in main to use the existing package. There is one
package golang-github-shopify-sarama (not updated since 2019) that has
{Build-,}Depends which include "golang-gopkg-eapache-go-resiliency.v1-
dev | golang-github-eapache-go-resiliency-dev". I'm not sure how `dak`
will handle this, but seeing as that package built well before I
introduced golang-github-eapache-go-resiliency, removing golang-github-
eapache-go-resiliency shouldn't cause any FTBFS in the archive.

Thanks,
Mathias

[signature.asc (application/pgp-signature, inline)]

Message #32 received at 1082307-close@bugs.debian.org (full text, mbox, reply):

From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>

To: 1082307-close@bugs.debian.org

Cc: golang-github-eapache-go-resiliency@packages.debian.org

Subject: Bug#1082307: Removed package(s) from unstable

Date: Mon, 02 Dec 2024 18:37:48 +0000

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

golang-github-eapache-go-resiliency |    1.7.0-1 | source
golang-github-eapache-go-resiliency-dev |    1.7.0-1 | all

------------------- Reason -------------------
ROM; accidental duplicate
----------------------------------------------

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1082307@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1082307

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)

Send a report that this bug log contains spam.