Otto Kekäläinen <[email protected]> writes: > All Go team packages should have a debian/gbp.conf that defines the > per-package conventions. Doing the upstream import should always be > done by issuing simply: > > gbp import-orig --uscan > > ..and it will do the correct thing based on debian/gbp.conf contents.
Running 'dh-make-golang' suggests to use this: git fetch github # note the latest tag or commit-ish uscan --report-status # check we get the same tag or commit-ish gbp import-orig --sign-tags --uscan --upstream-vcs-tag=<commit-ish> The Go team policy doesn't seem to be explicit how upstream sources should be imported into Salsa. I historically ignored dh-make-golang's advice here, but recently started to use it when I noticed that an existing package used that style. I think 'gbp import-orig --uscan --sign-tags' is a good command to use, so maybe we should say that in the policy? And say that debian/gbp.conf should be setup so that this command does the right thing? I'm not sure --upstream-vcs-tag=<commit-ish> can be set in debian/gbp.conf in any reasonable way though...? Setting 'upstream-tag=' doesn't achieve exactly the same, I think. /Simon
signature.asc
Description: PGP signature
