On Wed, Jun 3, 2026 at 8:03 PM Daniel Baumann <[email protected]> wrote: > > Package: golang-github-willf-bloom > Severity: normal > > Hi, > > I've uploaded golang-github-bits-and-blooms-bloom as a depends to > another package I maintain, turns out, this previously was known as > golang-github-willf-bloom. >
Sorry to cause confusion. It's my laziness to go through NEW queue in 2021, https://tracker.debian.org/news/1260694/accepted-golang-github-willf-bloom-301-2-source-into-unstable/ When upstream rename their repo, we should rename our source/binary package name. Since src:golang-github-bits-and-blooms-bloom has a higher version, I think you could just take over the binary package name (aka golang-github-willf-bloom-dev) in src:golang-github-bits-and-blooms-bloom as a transitional package. > Naturally, the two conflict now and we should get rid of one or the other. > > I think we have the following options, please let me know which one you > want to go with: > > A) We'll remove your golang-github-willf-bloom in favour of > my golang-github-bits-and-blooms-bloom > > => there's only one depends/reverse-depends: > golang-github-arceliar-ironwood > > the current upstream version also switched to > golang-github-bits-and-blooms-bloom > > I can take care about both of this if you want. > > B) you take over my golang-github-bits-and-blooms-bloom, > update golang-github-arceliar-ironwood and remove > your golang-github-willf-bloom. > > Regards, > Daniel -- Shengjing Zhu
