For the record, see https://github.com/Debian/dh-make-golang/issues/107 for discussion. tl;dr: https://bugs.debian.org/908204
On Sat, Dec 1, 2018 at 6:24 PM Tong Sun <[email protected]> wrote: > Hi, > > I'm trying to make my initial gbp push to salsa-project but I'm > wondering if it should be the suggested way: > > Here is what I'm trying to follow: > > 2018/11/25 09:07:42 To create the packaging git repository on salsa, use: > 2018/11/25 09:07:42 dh-make-golang create-salsa-project > golang-github-danverbraganza-varcaser > 2018/11/25 09:07:42 > 2018/11/25 09:07:42 Once you are happy with your packaging, push it to > salsa using: > 2018/11/25 09:07:42 git remote set-url origin > [email protected]: > go-team/packages/golang-github-danverbraganza-varcaser.git > 2018/11/25 09:07:42 gbp push > ^^^^^^^^ > > Here is my work log: > > $ git branch -v > * master 9078e4c - [+] Initial packaging > pristine-tar fbba72a pristine-tar data for > golang-github-danverbraganza-varcaser_0.0~git20151108.ce61ec4.orig.tar.xz > upstream 88a5d5c New upstream version 0.0~git20151108.ce61ec4 > > $ gbp push --dry-run --verbose > gbp:debug: ['git', 'rev-parse', '--show-cdup'] > gbp:debug: ['git', 'rev-parse', '--is-bare-repository'] > gbp:debug: ['git', 'rev-parse', '--git-dir'] > gbp:debug: ['git', 'symbolic-ref', 'HEAD'] > gbp:debug: ['git', 'show-ref', 'refs/heads/master'] > gbp:debug: ['git', 'config', 'branch.master.remote'] > gbp:debug: ['git', 'tag', '-l', 'debian/0.0_git20151108.ce61ec4-1'] > gbp:debug: ['git', 'tag', '-l', 'upstream/0.0_git20151108.ce61ec4'] > gbp:debug: ['git', 'rev-parse', '--quiet', '--verify', > 'upstream/0.0_git20151108.ce61ec4^{commit}'] > gbp:debug: ['git', 'rev-parse', '--quiet', '--verify', > 'refs/heads/upstream'] > gbp:debug: ['git', 'show-ref', '--verify', 'refs/heads/pristine-tar'] > gbp:debug: ['git', 'log', '--pretty=format:%H', '--no-merges', > '--grep=pristine-tar .* > golang-github-danverbraganza-varcaser_0.0~git20151108.ce61ec4.orig.tar.*', > 'pristine-tar', '--'] > gbp:debug: Found pristine-tar commit at > '31cf4b66f3eb7b7391cd90ddba762acb37ee6ea9' > gbp:debug: ['git', 'rev-parse', '--quiet', '--verify', > '31cf4b66f3eb7b7391cd90ddba762acb37ee6ea9^{commit}'] > gbp:debug: ['git', 'rev-parse', '--quiet', '--verify', > 'refs/heads/pristine-tar'] > gbp:info: Dry-run: Pushing upstream/0.0_git20151108.ce61ec4 to origin > gbp:debug: ['git', 'push', 'origin', 'tag', > 'upstream/0.0_git20151108.ce61ec4', '--dry-run'] > gbp:info: Dry-run: Pushing refs/heads/pristine-tar to > origin:refs/heads/pristine-tar > gbp:debug: ['git', 'push', 'origin', '--dry-run', > 'refs/heads/pristine-tar:refs/heads/pristine-tar'] > gbp:info: Dry-run: Pushing refs/heads/upstream to > origin:refs/heads/upstream > gbp:debug: ['git', 'push', 'origin', '--dry-run', > 'refs/heads/upstream:refs/heads/upstream'] > > I.e., I see that the first branch being pushed is *upstream* and I > don't see my default master branch being pushed at all. Is it correct? > > $ apt-cache policy git-buildpackage > git-buildpackage: > Installed: 0.9.10+nmu1 > Candidate: 0.9.10+nmu1 > Version table: > *** 0.9.10+nmu1 100 > 50 http://cdn-fastly.deb.debian.org/debian unstable/main amd64 > Packages > 100 /var/lib/dpkg/status > 0.8.12.2 500 > 500 http://cdn-fastly.deb.debian.org/debian stretch/main amd64 > Packages > > I was wondering, shall I follow `gbp push` as advised, or should I do > the following > > git push git+ssh://git.debian.org/git/pkg-go/packages/....git --tags > master pristine-tar upstream > > as per > https://people.debian.org/~stapelberg/2015/07/27/dh-make-golang.html? > > But I found nobody caution people not to use `gbp push`, so I gave it a > try. > And it turns out that golang-github-danverbraganza-varcaser's default > branch is indeed upstream and my default master branch was indeed not > being pushed at all. > > Comments? > What's the correct way to do the initial push? > > Can someone remove the golang-github-danverbraganza-varcaser repo > > https://salsa.debian.org/go-team/packages/golang-github-danverbraganza-varcaser > and let me try again please? > Done. > > Thx. > > -- Best regards, Michael
