"jani.p.heikkinen" <[email protected]> writes:
> Dear Go Team, > > I've been trying to figure out what is the correct workflow to do a > simple upstream version upgrade for an existing go package. > > Some developers suggest doing gbp import-origin --uscan. Yes. Or consider the tag2upload preferred workflow with import-ref. I suspect we'll eventually migrate to that although I haven't found time to integrate this into my personal workflow just yet. I find the reliance on 'gbp' for packaging mostly obsolete these days though. > It is a bit confusing against the advice in > https://go-team.pages.debian.net/packaging.html > where the workfow suggests doing some more complicated steps. I think those steps pretty much amount to the same thing as 'gbp import-orig --uscan' though. The text was written 5-10 years ago, I suspect import-orig didn't exist or wasn't behaving properly then. > Is https://go-team.pages.debian.net/ the source that should be used > when packaging? Hopefully yes. Thanks for raising what appears problematic with the current document. Re-reading things, I think the sections under 'Migration' and 'Packaging new upstream release' under https://go-team.pages.debian.net/packaging.html#wf-2017-11-upstream-branch could be replaced by an example using 'gbp import-orig --uscan' and a recommendation to configure debian/watch and possibly debian/gbp.conf to make that work, and note that 'dh-make-golang' should set things up automatically already. /Simon
signature.asc
Description: PGP signature
