Hi Thank you! I built and uploaded this now.
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. Is the step after that to request removal of the old package? 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. /Simon Nicolas Schier <nico...@fjasle.eu> writes: > Hi go-team, > > I am looking for someone in the team to review (and hopefully upload) > golang-gitlab-api-client-go. It is required for upcoming glab 1.52.0-1. > > https://salsa.debian.org/go-team/packages/golang-github-xanzy-go-gitlab > > > Upstream's repository has moved, thus I did a package rename following [1]. > If the packaging passes the review, it would be great if someone could rename > the repository. > > I had to disable some test, that fail during dpkg-buildpackage and sbuild, but > succeed when running 'make test'. My go-packaging-foo is not good enough yet > to solve this properly. > > Thanks and kind regards, > Nicolas > > > [1]: https://go-team.pages.debian.net/packaging.html
signature.asc
Description: PGP signature
