<div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Fri, Jun 15, 2018 at 7:55 PM Anthony Fok wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Fri, Jun 15, 2018 at 2:02 PM, Tong Sun wrote:<br><br>
>> 2. Check debian/gbp.conf, and if it is using "debian/sid" branch, the<br>
>> lines<br>
>><br>
>> [DEFAULT]<br>
>> ...<br>
>> debian-branch = debian/sid<br>
>><br>
>> [buildpackage]<br>
>> dist = DEP14<br>
>><br>
>> must be there.<br>
><br>
><br>
> Oh, thanks, I followed that 2017-11 Workflow Changes document word for word<br>
> and end up with a debian/gbp.conf of one single line:<br>
><br>
> $ cat debian/gbp.conf<br>
> [DEFAULT]<br>
<br>
That is equivalent to not having a debian/gbp.conf.<br>
And it appears that your debian/gbp.conf is problematic.<br>
<br>
Try going into a temporary directory and run:<br>
<br>
gbp clone git@salsa.debian.org:go-team/packages/golang-github-danverbraganza-varcaser.git<br>
<br>
and see if it works or not... </blockquote><div><br></div><div>You're right, it is problematic:</div><div><br></div><div>$ gbp clone git@salsa.debian.org:go-team/packages/golang-github-danverbraganza-varcaser.git</div><div>gbp:info: Cloning from 'git@salsa.debian.org:go-team/packages/golang-github-danverbraganza-varcaser.git'</div><div>gbp:error: Git command failed: Error running git checkout: error: pathspec 'master' did not match any file(s) known to git.</div><div><br></div><div>But if you follow <a href="https://people.debian.org/~stapelberg/2015/07/27/dh-make-golang.html">https://people.debian.org/~stapelberg/2015/07/27/dh-make-golang.html</a></div><div>then <a href="https://go-team.pages.debian.net/workflow-changes.html">https://go-team.pages.debian.net/workflow-changes.html</a> </div><div><br></div><div>You will end up with a problematic debian/gbp.conf <i><b>exactly</b></i> as mine. </div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">And compare the result with<br>
<br>
gbp clone git@salsa.debian.org:go-team/packages/golang-x-text.git<br>
<br>
The Workflow Changes document is a proposal for action, not a<br>
step-by-step guide, so, no, I didn't find the answers there either.<br>
Instead, I found those debian/gbp.conf in packages like the following<br>
(which I happened to have cloned locally):<br>
<br>
* elvish<br>
* golang-golang-x-tools<br>
* golang-golang-x-net-dev [*]<br>
* golang-x-text<br>
* golang-github-prometheus-tsdb<br>
<br>
golang-golang-x-net-dev is a misnomer, as the following comment in its<br>
debian/control states:<br>
<br>
# XXX: This source package should be called golang-golang-x-net, the -dev<br>
# suffix is a mistake. --stapelberg<br>
Source: golang-golang-x-net-dev<br>
<br>Personally, for debian/gbp.conf, I am just using whatever<br>
dh-make-golang creates by default.<br>
But there is no one right answer. The pkg-go team seems to be<br>
exploring that too, and everybody does it slightly differently.<br>
<br>
> Having seen you remaining on the master branch instead of changing to<br>
> debian/sid, maybe I should do too, to my next package.<br>
<br>
It is entirely up to you, until the pkg-go team come up with a<br>
standard debian/gbp.conf that everyone follows.<br>
Not too important, and we survive thus far, but indeed I would love<br>
that all Go related pacages get a unified debian/gbp.conf...<br></blockquote><div><br></div><div>Indeed, </div><div><br></div><div>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:</div><div><a href="https://salsa.debian.org/go-team/packages/packer/blob/debian/sid/debian/gbp.conf">https://salsa.debian.org/go-team/packages/packer/blob/debian/sid/debian/gbp.conf</a><br></div><div><br></div><div>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. </div><div><br></div><div><br></div><div><br></div><div><br></div></div></div>