[git-buildpackage] gbp does not recognize the newly merged & tagged upstream version

[Guido Günther]

Hi Lukasz,
On Thu, Apr 20, 2017 at 11:28:25AM +0000, Lukasz Walewski wrote:
> Hi,
> 
> I am trying to use git-buildpackage to build debian packages with custom software managed in a git repo. The software is developed by a local team and releases are marked with git tags only, no upstream tarballs are available. I tried to follow the documentation (http://honk.sigxcpu.org/projects/git-buildpackage/manual-html/gbp.import.html#GBP.IMPORT.UPSTREAM-GIT) and configured my debian branch accordingly.
> 
> I was able to create the package with the initial version of my software, which was tagged as 'v1.0.2'. However, I am not able to merge the next "upstream" release tagged 'v1.0.3'. I do the following:
> 
> git checkout debian
> git fetch
> git merge v1.0.3
> gbp dch --snapshot --auto
> gbp buildpackage --git-ignore-new -us -uc
> 
> But, gbp builds the version 1.0.2 and does not capture the 1.0.3:
> 
> dpkg-buildpackage: source version 1.0.2-2
> 
> I got somehow lost and cannot find out what am I doing wrong. I would be grateful for any help.

This is very likely because you didn't tell gbp how your upstream tags
look like. It usually expects tags of the form

    upstream/<version>

but it can be configured via the --upstream-tag option. You can also do
this in your gbp.conf, see e.g.

    https://github.com/agx/ldapsp/blob/debian/sid/debian/gbp.conf

where I'm using a setup that is very similar to yours.
Cheers,
 -- Guido