On Mon, Jun 20, 2016 at 02:11:37PM +1000, Dmitry Smirnov wrote:
> 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.

Please add the instruction to debian/README.source

See https://www.debian.org/doc/debian-policy/ch-source.html#s-readmesource
for more informatin on that file. Snippet from that section:

  debian/README.source may also include any other information that would
  be helpful to someone modifying the source package.

> -- 
> 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

So true

Geert Stappers
Leven en laten leven

Pkg-go-maintainers mailing list

Reply via email to