Talking to myself a little, I learned about about the naming policy: https://go-team.pages.debian.net/packaging.html#_upstream_package_moves I have updated the package and believe what's in https://salsa.debian.org/jas/golang-github-go-redis-redis should be uploaded to unstable. Can someone please review my changes? And think about if the reverse dependencies works or not with v9? I haven't learnt how to use 'ratt' to test this myself, so if someone can build my version of the package and run it, that would be appreciated! /Simon Simon Josefsson <simon@josefsson.org> writes: > Hi > > I am working on packaging github.com/sigstore/rekor which has a large > number of dependencies. > > One of them is 'github.com/redis/go-redis' (version 9) and there is an > existing package 'golang-github-go-redis-redis' (for version 6) in > Debian that packages the old name of this project > 'github.com/go-redis/redis' (note slight change compared to first name). > > I have updated that package for v9 here, and it builds okay: > > https://salsa.debian.org/jas/golang-github-go-redis-redis/ > https://salsa.debian.org/jas/golang-github-go-redis-redis/-/pipelines > > How should this be resolved? Some ways forward: > > 1) Ignore the existing 'golang-github-go-redis-redis' package and ITP a > new package for the new source name 'golang-github-redis-go-redis' and > package v9 there. > > 2) Upload v9 in the existing 'golang-github-go-redis-redis' source > package using the old binary package 'golang-github-go-redis-redis-dev'. > > 3) Upload v9 in the existing 'golang-github-go-redis-redis' source > package using a new binary package 'golang-github-redis-go-redis-dev' > that better reflect the current upstream name. > > 4) ? > > /Simon >
Attachment:
signature.asc
Description: PGP signature