On 08/10/2025 08:11, Richard Hansen wrote:
For a new package, what should I do once I feel that it is ready to be uploaded? Should I go ahead and create the project in salsa.d.o/go- team/packages using dh-make-golang and push the commits there? Or should I get someone else to review my commits in my personal namespace before pushing to a new go-team project?
For my first package, I definitely pushed it to my own namespace so I can be owner, run the pipeline and fix and force-push whatever I wanted. Even if your Vcs-* fields point at go-team repos, do a practice gbp-push first then see if you can do a fresh gbp-clone/gbp-buildpackage without any changes. The go-team doesn't seem to use mentors.d.n or RFS process, but a practice `dput mentors` was interesting too (but it has an old lintian).
Also, perhaps consider using the standard debian "salsa-ci.yml" pipeline file, not the generated one, as that actually builds/tests the package.
Here is an example: https://salsa.debian.org/go-team/packages/pixelmatch -- Regards, Ahmad
