Package: git-buildpackage Version: 0.7.5 Severity: wishlist Dear Maintainer,
as you might have noticed, i'm discovering the joys of gbp hooks and keep coming up with new issues... now: would it be possible to make the upstream version of the just-imported package available to a postimport-hook? in theory one could use dpkg-parsechangelog and mangle the debian version to the upstream version. but this is fragile, and gbp know the upstream-version anyhow, so why not use it directly. i'm dreaming of having a GBP_UPSTREAM_VERSION environment variable. (and while you are there, you could add a GBP_DEBIAN_VERSION variable as well, so there is *no* need at all to call dpkg-parsechangelog) such an env-variable (or a different one) could also be used to "determine" whether the hook is run from gbp or directly (something i eventually would like to know) thanks for your kind attentions. -- System Information: Debian Release: stretch/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.6.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=de_AT.utf8, LC_CTYPE=de_AT.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.6 ii git 1:2.8.1-1 ii man-db 2.7.5-1 ii python-dateutil 2.4.2-1 ii python-pkg-resources 20.10.1-1.1 ii python-six 1.10.0-3 pn python:any <none> Versions of packages git-buildpackage recommends: ii cowbuilder 0.80 ii pbuilder 0.225.2 ii pristine-tar 1.34 ii python-requests 2.10.0-2 Versions of packages git-buildpackage suggests: ii python-notify 0.1.1-4 ii sudo 1.8.17p1-2 ii unzip 6.0-20 -- no debconf information
