On Sunday, 19 June 2016 9:59:30 PM AEST Martín Ferrari wrote: > On 19/06/16 20:47, Dmitry Smirnov wrote: > > I would be happy to upload updated package but I've noticed that > > "upstream" branch follows upstream history so "gbp import-orig" would > > break it and I'm not sure how to handle such repository configuration... > > I have just done it. These are the steps: > [...]
Thank you, Martin. :) I think your procedure could be improved if "git merge upstream/2.1" is modified with "--squash" to produce one neat merge commit to "master" instead of flood of upstream commits that make it difficult to identify packaging-related commits. Merge from upstream branch that follows upstream history makes it difficult to review packaging changes therefore I see it as counter-productive especially for team-maintained packages. I do not mind having full upstream history in "upstream" branch but not in "master"... > I am just confused > as to why you removed the Build-Using field in control.. Because it was used on arch-all -dev package shipping sources... Built-Using on -dev packages is an artifact of older versions of dh-make- golang which do not add "Built-Using" to -dev packages any more. Anyway "Built-Using" is not meant to be used with -dev packages. Built-Using field is usually applied to binaries incorporating portion of another package or built using another package without explicit dependency. -dev packages should already depend on all related -dev dependencies. -- Cheers, Dmitry Smirnov. --- I believe in only one thing: liberty; but I do not believe in liberty enough to want to force it upon anyone. -- H. L. Mencken
Description: This is a digitally signed message part.
_______________________________________________ Pkg-go-maintainers mailing list Pkgfirstname.lastname@example.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers