[pkg-go] You are not allowed to push code to this project

[Tong Sun]

On Fri, Jun 15, 2018 at 7:55 PM Anthony Fok  wrote:

> On Fri, Jun 15, 2018 at 2:02 PM, Tong Sun  wrote:
>
> >>  2. Check debian/gbp.conf, and if it is using "debian/sid" branch, the
> >> lines
> >>
> >>         [DEFAULT]
> >>         ...
> >>         debian-branch = debian/sid
> >>
> >>         [buildpackage]
> >>         dist = DEP14
> >>
> >>      must be there.
> >
> >
> > Oh, thanks, I followed that 2017-11 Workflow Changes document word for
> word
> > and end up with a debian/gbp.conf of one single line:
> >
> > $ cat debian/gbp.conf
> > [DEFAULT]
>
> That is equivalent to not having a debian/gbp.conf.
> And it appears that your debian/gbp.conf is problematic.
>
> Try going into a temporary directory and run:
>
>     gbp clone git at salsa.debian.org:
> go-team/packages/golang-github-danverbraganza-varcaser.git
>
> and see if it works or not...


You're right, it is problematic:

$ gbp clone git at salsa.debian.org:
go-team/packages/golang-github-danverbraganza-varcaser.git
gbp:info: Cloning from 'git at salsa.debian.org:
go-team/packages/golang-github-danverbraganza-varcaser.git'
gbp:error: Git command failed: Error running git checkout: error: pathspec
'master' did not match any file(s) known to git.

But if you follow
https://people.debian.org/~stapelberg/2015/07/27/dh-make-golang.html
then https://go-team.pages.debian.net/workflow-changes.html

You will end up with a problematic debian/gbp.conf *exactly* as mine.

And compare the result with
>
>     gbp clone git at salsa.debian.org:go-team/packages/golang-x-text.git
>
> The Workflow Changes document is a proposal for action, not a
> step-by-step guide, so, no, I didn't find the answers there either.
> Instead, I found those debian/gbp.conf in packages like the following
> (which I happened to have cloned locally):
>
>   * elvish
>   * golang-golang-x-tools
>   * golang-golang-x-net-dev [*]
>   * golang-x-text
>   * golang-github-prometheus-tsdb
>
> golang-golang-x-net-dev is a misnomer, as the following comment in its
> debian/control states:
>
>    # XXX: This source package should be called golang-golang-x-net, the
> -dev
>    # suffix is a mistake. --stapelberg
>    Source: golang-golang-x-net-dev
>
> Personally, for debian/gbp.conf, I am just using whatever
> dh-make-golang creates by default.
> But there is no one right answer.  The pkg-go team seems to be
> exploring that too, and everybody does it slightly differently.
>
> > Having seen you remaining on the master branch instead of changing to
> > debian/sid, maybe I should do too, to my next package.
>
> It is entirely up to you, until the pkg-go team come up with a
> standard debian/gbp.conf that everyone follows.
> Not too important, and we survive thus far, but indeed I would love
> that all Go related pacages get a unified debian/gbp.conf...
>

Indeed,

While I was trying to find more examples, I found people are
having gbp.conf with all kinds of combinations, like the following one,
which has debian/sid branch, but not your above setting what so ever, and
it even has the pristine-tar branch as well:
https://salsa.debian.org/go-team/packages/packer/blob/debian/sid/debian/gbp.conf

Well, I now know that at least the gbp.conf file come straight from `gbp
clone` without any modification. if new packers will try to find a
good gbp.conf settings, then looking into existing code will be confusing
at best. A standard is badly needed, at least a gold example that is not
too complicated to carry away the gist is the very least needed.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-go-maintainers/attachments/20180615/3e641003/attachment.html>