On Wed, Apr 9, 2025 at 11:26 PM Simon Josefsson <si...@josefsson.org> wrote:
> Thank you! Some observations - tl;dr: I suggest to remove > golang-step-crypto-dev from the archive as discussed in 1) below, and > for us to ignore issue 2) + 3) below, even though they warrant more > consideration. > > 1) Now there are no reverse dependencies on golang-step-crypto-dev any > more, so I think we could ask for removal of that package from the > archive which would resolve https://bugs.debian.org/1100967 > [...] > > 2) However I realized I was wrong in my comment in > https://bugs.debian.org/1100967#10 about which package name is the > "proper" one. Upstream's go.mod namespace is still go.step.sm/crypto > even in latest upstream master: > > https://github.com/smallstep/crypto/blob/master/go.mod > > So then the "correct" package name in Debian really ought to be > "golang-step-crypto" after all.... sigh. Should we upload > golang-step-crypto v0.60.0 and migrate all dependencies back to the > proper name, and then remove golang-github-smallstep-crypto? Sorry for the late reply. But I think it can be better handled. We can just update golang-step-crypto to 0.57.0-1 and make golang-github-smallstep-crypto-dev as a transitional package. I prefer we keep the correct package name, aka golang-step-crypto. -- Shengjing Zhu
