Nicolas Schier <nico...@fjasle.eu> writes: >> Since it is a NEW upload, I suppose there are no reverse-build >> considerations?! I can fix cosign to use your package, assuming it >> builds with your new package (I did not test, did you?) instead of the >> old package name. > > Oh, I hadn't thought about reverse-build dependencies, thanks for the > reminder! > I successfully built cosign on amd64 also with > golang-gitlab-api-client-go/0.123.0-1 now, but I have not done any runtime > testing except calling 'cosign --help'.
Great! >> Is the step after that to request removal of the old package? > > I have no experience with golang package renames. If cosign is really the > only > other user (except glab), I'd guess, that removal would make sense, but I am > still a go-packaging-greenhorn. Me too, so let's learn during this excersise. There was some other package that I needed to do this for too that is on my todo list. When is the appropriate time to rename the old git repository on Salsa? When it has been accepted through the NEW queue perhaps? Maybe the upload should have gone via debian/experimental branch to not mess up debian/sid in case we need to do uploads of the old package (or the package is never accepted). But reverting commits are easy so no big issue. Alternatively, just fork the git repository into the new name on Salsa and let the old name continue exist on Salsa? I'm not sure if we have a clear workflow documentation on this. >> Why did you use dh-golang instead of dh-sequence-golang? I thought the >> migration should be TOWARDS dh-sequence-golang, not from it? And stop >> using --with=golang. Doesn't modern dh-make-golang do this? This can >> be fixed once it is in the archive, though, unless I'm wrong. > > That's my fault. I confused myself by accidentally using an old > dh-make-golang > version from stable. I am going going to fix up. Thank you! > Does it make sense to finalize packaging of glab 1.52.0-1 (using > golang-gitlab-api-client-go), or should I delay that until the package is > accepted? That's not possible now, right? You have to wait until the package has been through the NEW queue. If you are talking about Salsa pipeline builds, then that's perfectly possible now though. /Simon
signature.asc
Description: PGP signature
