[pkg-go] fscrypt: commit to the upstream branch

Michael Stapelberg stapelberg at debian.org
Mon May 14 17:38:23 BST 2018

[+cc pkg-go-maintainers, because others might have thoughts on this topic,

On Thu, May 10, 2018 at 9:29 PM, Paride Legovini <pl at ninthfloor.org> wrote:

> Hello Michael,
> I noticed that you committed gitlab-ci.yml to fscrypt's upstream branch:
> https://salsa.debian.org/go-team/packages/fscrypt/commits/master
> I suppose this was not intentional, and happened because fscrypt is one
> of the few repositories following DEP14 (where master=upstream). If this
> was intentional, then I'm clearly missing something :)

Your assertion that DEP-14 uses master=upstream came as a bit of a surprise
to me. After another reading of DEP-14, I conclude that this isn’t
sufficiently clearly specified, if it is indeed intentioned.

The “Managing upstream sources” section talks about upstream/* branches
only in the context of importing release tarballs.

The “Importing upstream releases from Git tags” subsection doesn’t mention
any branch names.

The only section which explicitly talks about the master branch is the
“Native packages” section, which doesn’t apply to the case at hand.

I was under the impression that “upstream” is the branch name one should
use for upstream sources, but as outlined above, that isn’t specified
either. I think it would be good to file this is an issue against DEP-14.
What do others think?

> If it was not intentional, could you please revert (or reset) it?
> Thank you,
> Paride

Best regards,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-go-maintainers/attachments/20180514/a0132251/attachment.html>

More information about the Pkg-go-maintainers mailing list