[git-buildpackage] gbp push without upstream branch

[Markus Blatt]

Hi,

I am trying to convert some of Packages to git-buildpackage and am struggling a bit about how to do that
with an upstream branch.

E.g. for dune-common [1] I have this:

- No upstream branch as upstream uses git and we do not need to remove any files.
- debian-branch is debian/latest. We used to only have the debian directory here (See old master branch).
   But for git-buildpackage I have started to merge the upstream releases by tags.
- I have a pristine-tar branch that gets commit when building (--git-pristine-tar-commit)

I had hoped that could use gbp push, but I am failing and currently push with git manually.

First time I tried I got:

gbp:error: revision 'upstream/2.11.0^{commit}' not found

I simply created that tag directly on the commit that is tagged as the upstream release.

Now I get:

gbp:error: revision 'refs/heads/upstream' not found

So it seems like gbp assumes upstream branches. Is there a way to make gbp push work for my setting?

I use gbp 0.9.30 any my gbp.conf is

DEFAULT]
debian-branch = debian/latest
#upstream-branch = upstream/latest
pristine-tar = True
#upstream-vcs-tag = v%(version)s

[git-buildpackage]
upstream-tag = v%(version)s

Best,

Markus

[1] <https://salsa.debian.org/science-team/dune-common>