Dear team,

Looking for some advice here:

Per bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1139314, the
upstream for the above package moved to codeberg. I updated and
renamed the source package and pushed the changes to salsa [0]
recently.

  [0] 
https://salsa.debian.org/go-team/packages/golang-code.rocketnine-tslocum-cbind

However, 10 days after the above bug was filed, another team member
(ajqlee) separately filed an ITP and directly uploaded the library to
salsa [0] and the archive, with no reference to the existing source
package, bug report, salsa repository [1] or current reverse deps. Per
the ITP it is a dep for golang-github-noborus-ov.

  [1] https://salsa.debian.org/go-team/packages/golang-codeberg-tslocum-cbind


Observations:

*)  there are now 2 different versions of the same library in the
archive under different package names, and 2 different salsa repos

*) the new salsa repository has no history of previous Debian releases

*) the existing salsa repository maintains the history and provides
the same upstream source version, but which is not in the archive

*) the reverse dependencies using this library are not updated
(AFAICS) to use the new package name


The ideal situation would seem to be to have the full Debian release
history of the renamed library package available in a single repo on
salsa (as with previous Go package renames).

How best to proceed?

Thanks,
Nick

Reply via email to