I've found yet another variant on how to maintain multiple versions of the same package: golang-github-jackc-puddle. It uses the same Salsa project for both v1 and v2, but keep packaging on different branches, instead of setting up different Salsa projects for each package. This has the nice property of have similar code in the same git repository, for easier cherry picking, but for a package with releases on multiple versions (which isn't uncommon) I think this approach would be messy.
(This particular package has a bug in that the Vcs-* URLs should have a '-b debian/v2/sid' for the golang-github-jackc-puddle-v2 packaging.) At this point, I've given up my hope to ever be able to harmonize on one single Debian workflow for Go projects with multiple vX, vY branches. It would still be nice to get one approach explained and documented in the Go team policy, so that not everyone will have to go through the same learning curve about this topic. /Simon
signature.asc
Description: PGP signature
