Package: gitpkg
Version: 0.28
Severity: normal
File: /usr/bin/git-debcherry
TL;DR, git-debcherry (or maybe just gitpkg's invocation of it) should
likely force resolving the given treeish to a non-tag with ^{}.
$ debcheckout neovim-qt && cd neovim-qt
…
$ git-debcherry -o ../bug v0.2.8 v0.2.8-2
Cloning into '/tmp/git-debcherry.KYsPnT/clone'...
done.
$ cat ../bug/0001-Point-gbp-dch-to-the-correct-branch.patch
From bacc7ba0767f29425a9083d1ae08390f93daede0 Mon Sep 17 00:00:00 2001
From: James McCoy <james...@debian.org>
Date: Tue, 16 Jan 2018 07:31:37 -0500
Subject: [PATCH] Point gbp-dch to the correct branch
Signed-off-by: James McCoy <james...@debian.org>
---
debian/gbp.conf | 2 ++
1 file changed, 2 insertions(+)
create mode 100644 debian/gbp.conf
diff --git a/debian/gbp.conf b/debian/gbp.conf
new file mode 100644
index 0000000..c295a2a
--- /dev/null
+++ b/debian/gbp.conf
@@ -0,0 +1,2 @@
+[dch]
+debian-branch = debian/sid
$ rm -r ../bug
$ git-debcherry -o ../bug v0.2.8 v0.2.8-2^{}
Cloning into '/tmp/git-debcherry.RxnlzO/clone'...
done.
Warning: no patches exported
I usually encounter this when I'm doing the final gitpkg run before
uploading a package. I adjust the changelog, tag the debian version,
and then run either “gitpkg debian/sid” or “gitpkg v0.2.8-2”. I'd
expect them to exhibit equivalent behavior, but as shown above the
latter fails.
-- System Information:
Debian Release: buster/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1,
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages gitpkg depends on:
ii dpkg-dev 1.19.0.5
ii git 1:2.15.1-3
gitpkg recommends no packages.
Versions of packages gitpkg suggests:
ii devscripts 2.17.12
-- no debconf information
