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

[Guido Günther]

On Thu, Apr 20, 2017 at 12:14:28PM +0000, Lukasz Walewski wrote:
> >-----Ursprüngliche Nachricht-----
> >Von: Guido Günther [mailto:agx at sigxcpu.org]
> >Gesendet: Donnerstag, 20. April 2017 14:03
> >An: Lukasz Walewski
> >Cc: git-buildpackage at lists.sigxcpu.org
> >Betreff: Re: [git-buildpackage] gbp does not recognize the newly merged
> >& tagged upstream version
> >
> >Hi Lukasz,
> 
> Hi Guido,
> 
> Thank you very much for the rapid answer!
> 
> >This is very likely because you didn't tell gbp how your upstream tags
> >look like.
> 
> Well, I think I did, but it can still be wrong... Here is my config file:
> 
> $ cat debian/gbp.conf
> [DEFAULT]
> debian-branch=debian
> upstream-branch=master
> 
> [buildpackage]
  ^^^^^^^^^^^^^^
means it only affects buildpackage but not dch (or nothing else), see
the link I posted:

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

> upstream-tag=v%(version)s

I kind of anticipated this when reading your post and already clarified
this in the docs:

    https://github.com/agx/git-buildpackage/commit/1bf6ef42e015775d4171e0874293df608123989b#diff-8900478ae00d90e6e5f85faba5b5abefR279

You can check if dch sees the right tag format by running

   $ gbp config dch.upstream-tag
   dch.upstream-tag=upstream/%(version)s

in the repository. It's recommended to put all of the tag and branch
configuration into [DEFAULT] since you usually want all tools to behave
the same.

> export-dir=build
> 
> The upstream tags are of the form vX.Y.Z, as seen here:
> 
> $ git tag
> debian/1.0.2-1
> debian/1.0.2-2
> v1.0.0
> v1.0.1
> v1.0.2
> v1.0.3
> 
> Any ideas?

Hope this helps,
 -- Guido