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

Lukasz Walewski lwalewski at s-can.at
Thu Apr 20 16:44:31 CEST 2017

>-----Ursprüngliche Nachricht-----
>Von: Guido Günther [mailto:agx at sigxcpu.org]
>Gesendet: Donnerstag, 20. April 2017 15:57
>An: Lukasz Walewski
>Cc: git-buildpackage at lists.sigxcpu.org
>Betreff: Re: [git-buildpackage] gbp does not recognize the newly merged
>& tagged upstream version
>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
>> $ cat debian/gbp.conf
>> debian-branch=debian
>> upstream-branch=master
>> [buildpackage]
>  ^^^^^^^^^^^^^^
>> upstream-tag=v%(version)s
>means it only affects buildpackage but not dch (or nothing else)

Oh! You are right, I overlooked that tiny detail!

>You can check if dch sees the right tag format

After fixing my gbp.conf according to your suggestions, (I think) I get the right upstream-tag:

$ gbp config dch.upstream-tag

However, after running dch and buildpackage I still get the wrong version. Interestingly, dch doesn't detect any changes in my working tree:

$ gbp dch --snapshot --auto
gbp:info: Changelog last touched at 'a1b2c3d4'
gbp:info: Continuing from commit 'a1b2c3d4'
gbp:info: No changes detected from a1b2c3d4 to HEAD.
gbp:info: Changelog has been prepared for snapshot #1 at a1b2c3d4

although I merged v1.0.3, which _does_ contain changes. Should I commit the merge first?

Apparently, we've found one bug in my setup (thanks for that!) but unfortunately it was not the only one...



scan Messtechnik GmbH
Brigittagasse 22-24
A-1200 Wien/Vienna
tel. +43 1 219 73 93 - 0
fax +43 1 219 73 93 - 12
office at s-can.at

Geschaeftsfuehrer/President: DI Andreas Weingartner
Firmenbuchnummer/Incorporation No: FN178880i
Gerichtsstand/Court of Jurisdiction: Wien/Vienna


s::can - intelligent, optical, online

i::scan - compact, precise and affordable!
UV254::NTU::FTU::TOC::DOC::COD::BOD::Colour ...and many more to come!

More information about the git-buildpackage mailing list