Your message dated Sun, 18 Mar 2018 18:05:23 +0000 with message-id <[email protected]> and subject line Bug#887963: fixed in gitpkg 0.29 has caused the Debian Bug report #887963, regarding git-debcherry: Exports incorrect patches when fed tags to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 887963: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887963 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---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 <[email protected]> Date: Tue, 16 Jan 2018 07:31:37 -0500 Subject: [PATCH] Point gbp-dch to the correct branch Signed-off-by: James McCoy <[email protected]> --- 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
--- End Message ---
--- Begin Message ---Source: gitpkg Source-Version: 0.29 We believe that the bug you reported is fixed in the latest version of gitpkg, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [email protected], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ron Lee <[email protected]> (supplier of updated gitpkg package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Sun, 18 Mar 2018 17:29:35 +1030 Source: gitpkg Binary: gitpkg Architecture: source all Version: 0.29 Distribution: unstable Urgency: medium Maintainer: Ron Lee <[email protected]> Changed-By: Ron Lee <[email protected]> Description: gitpkg - tools for maintaining Debian packages with git Closes: 820842 887963 Changes: gitpkg (0.29) unstable; urgency=medium . * Fix git-debcherry for a change in the behaviour of how git rev-parse handles tag refs. Thanks to James McCoy for spotting it and the initial patch to fix it. Closes: #887963 . * Support passing arbitrary options to the orig compressor, and default to passing -n (--no-name) to gzip, so that it doesn't add a timestamp, making the compressed orig tarball more reproducible. Thanks to Antoine Beaupré for noticing the current default behaviour, the idea of passing this option to gzip to improve it, and testing that it worked. The actual fix here is a bit different, because -n (meaning this) is specific to gzip, so now we have support for setting per-compressor options too. Closes: #820842 Checksums-Sha1: 70b005002fd54db3d3c1fa5b3152d6c3ec68aa1e 1459 gitpkg_0.29.dsc 42eb4b4d148092bd36d986ac195be5fd9a84c8aa 42356 gitpkg_0.29.tar.gz 5260035b4a881cb4718d8f8050f04c63895389d4 43318 gitpkg_0.29_all.deb Checksums-Sha256: 48578e9426805d548bef7587dad9eb32516c4b12eeaa5fc6f439b877468d4b97 1459 gitpkg_0.29.dsc a40b74dbf342af2b524180132a911696bdf007726319b190d0bab9490ff94f8d 42356 gitpkg_0.29.tar.gz bd1fe4c5ca8ab5aef79dceada79c78d6a6e7844d52b171ba6aed2d02618b3979 43318 gitpkg_0.29_all.deb Files: b58f6173cd613a1ad867ea281ced3191 1459 vcs optional gitpkg_0.29.dsc de1fa70e760d69256423d8d2fcd917ff 42356 vcs optional gitpkg_0.29.tar.gz f176f1775578e4b9fe162cc4b5792c08 43318 vcs optional gitpkg_0.29_all.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJarp/GAAoJECSWn9pgwHEsTJkP+QHSNzbjVXqPhAKp31rKfvvh gb38yNhMllabRm0L1OggHFWfwVsOC+S38opkH+cQVij0WzmhGBnQzyjc8GqrZYcN WKN3l3zlSpCjgwOcbTkKcnmpSpMnWts+Qz2n72P/8jrPopuscCtv8Cltgrv43CJn qtB2KgmUoDEYOhBXMDMncotLfumQhWSJbfgZ/Ad7dp9nZ/eRbJzfXxPetRjxKJU0 6hOAItUESiGyhYo5LPfwOgNpWf9Zpb2m9J0vkSWjy7L/pOx52/s51Ok7pGJAd6iC lk8zha22wHwAxIDiaIu4C58MVYR0MGPGB5N4snERyIQb/EBQhP9lRwEMpOVc3Oq4 uR2S00yezZptMf5LwrISq20MWo8p5dy7AudeADklbBDNWNEqg9HgD7U+1CXc6H8l EGCz4JK8LynI0ohAcbDRJCmG35LYRSJ1/ytimnRu0YTYZlmBP1HTbbN71czyxfLQ R66CKRJHoD2UPZRBcGGkGL29IXEkYD8jigTDfK7oQewbnYjQ2ZZz4uO470a7EP93 j5lZD0yrQjGRznPYae1TL8zJFjAdenS85pdlST/X9RLKpx/sBe88rGiRkYs6SJti /eifNSRO0gfzxGDow3aFzN+sDScluiOB9RCZDcZ7PjWsZLnbyJCmn6c6vJGzqk0p NO++nrH4GiRV5MOIeU+c =qarM -----END PGP SIGNATURE-----
--- End Message ---
