Package: git-buildpackage Version: 0.7.2 Severity: normal Hi,
the man page says: |If no arguments are given, gbp dch starts from the last tagged Debian |package version up to the current tip of the current branch. In practice, when on branch 'master', it says "Version not found": [63/560]mh@salida:~/packages/apg/apg$ gbp dch --verbose gbp:debug: ['git', 'rev-parse', '--show-cdup'] gbp:debug: ['git', 'rev-parse', '--is-bare-repository'] gbp:debug: ['git', 'symbolic-ref', 'HEAD'] gbp:debug: ['git', 'show-ref', 'refs/heads/master'] gbp:debug: ['git', 'tag', '-l', 'debian/2.2.3.dfsg.1-3'] gbp:debug: ['git', 'tag', '-l', 'debian/2.2.3.dfsg.1-3'] gbp:error: Version 2.2.3.dfsg.1-3 not found [64/561]mh@salida:~/packages/apg/apg$ this looks like gbp dch wants the new version to be already tagged, which is contraproductive since one usually wants the tag to sit right on the commit that was used to build for upload, hence _with_ the new changelog. I think that the documented behavior, using the "current tip of the current branch" should be the way to do things. So the code should be adapted. Greetings Marc -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.4.4-zgsrv20080 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages git-buildpackage depends on: ii devscripts 2.16.1 ii git 1:2.7.0-1 ii man-db 2.7.5-1 ii python-dateutil 2.4.2-1 ii python-pkg-resources 20.1.1-1 ii python-six 1.10.0-3 pn python:any <none> Versions of packages git-buildpackage recommends: ii pristine-tar 1.33 pn python-requests <none> ii sbuild 0.68.0-1 Versions of packages git-buildpackage suggests: pn python-notify <none> ii sudo 1.8.15-1.1 ii unzip 6.0-20 -- no debconf information
