On Wed, Jun 10, 2026 at 10:15 PM Daniel Baumann <[email protected]> wrote: > > Hi, > > On 6/9/26 22:10, Shengjing Zhu wrote: > > Sorry to cause confusion. > > no worries :) > > > 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. > > true; however, since a) it's a -dev package and b) there's only one > reverse-depends, I don't think that makes sense - especially since the > import path in the sources still needs to be adjusted for any package > that is build-depending on it. > > I think it's the better "feedback" to the user if the package doesn't > exist, rather than it exists but will fail to build. > > so, I'll then go forward with: > > * first, adding conflicts/replaces in golang-github-bits-and-blooms- > bloom against golang-github-willf-bloom > > * second, updating golang-github-arceliar-ironwood (filling bug+MR) > > * after that, filling RM bug against golang-github-willf-bloom > > ok with you?
Yes, please go ahead. -- Shengjing Zhu
