Your message dated Mon, 21 Sep 2026 00:19:00 +0000
with message-id <[email protected]>
and subject line Bug#1105759: fixed in dgit 17.0
has caused the Debian Bug report #1105759,
regarding want git-debpush to read upstream tag pattern from gbp.conf
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.)
--
1105759: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1105759
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: git-debpush
Version: 12.12
Severity: wishlist
I got this error:
jas@kaka:~/dpkg/git2cl$ git debpush --gbp --tag-only
tags upstream/3.0, v3.0 all exist in this repository
tell me which one you want to make an orig.tar from: git deborig --just-print
'--version=1:3.0-3' TAG
git-debpush: git-deborig failed; maybe try git-debpush --upstream=TAG
jas@kaka:~/dpkg/git2cl$
The message is correct, but I don't understand why it is confused by the
unrelated v3.0 tag.
jas@kaka:~/dpkg/git2cl$ cat debian/gbp.conf
[DEFAULT]
debian-branch = debian/latest
upstream-branch = upstream/latest
pristine-tar = True
jas@kaka:~/dpkg/git2cl$
I thought gbp defaults where to use upstream/* so v3.0 doesn't match here:
--upstream-tag=tag-format
Use this tag format when tagging upstream versions, default is
upstream/%(version)s.
Here is my upstream branch:
jas@kaka:~/dpkg/git2cl$ git log -1 upstream/latest
commit b2866e9a66b43855a37e462d17a8ba1ca3c51d90 (tag: upstream/3.0,
origin/upstream/latest, jas/upstream/latest, upstream/latest)
Author: Simon Josefsson <[email protected]>
Date: Wed Oct 9 15:56:31 2024 +0200
New upstream version 3.0
jas@kaka:~/dpkg/git2cl$
The v3.0 tag is coming from my upstreamvcs remote:
jas@kaka:~/dpkg/git2cl$ git remote -v
dgit
jas [email protected]:jas/git2cl.git (fetch)
jas [email protected]:jas/git2cl.git (push)
origin [email protected]:debian/git2cl.git (fetch)
origin [email protected]:debian/git2cl.git (push)
upstreamvcs https://git.savannah.gnu.org/git/git2cl.git (fetch)
upstreamvcs https://git.savannah.gnu.org/git/git2cl.git (push)
jas@kaka:~/dpkg/git2cl$ git log -1 upstreamvcs/master
commit 78455e00db59155469212fecae1362be00eb8754 (tag: v3.0, tag: git2cl-3.0,
upstreamvcs/master)
Author: Simon Josefsson <[email protected]>
Date: Wed Oct 9 15:16:43 2024 +0200
Fix git2cl POD doc.
Reported by Reuben Thomas <[email protected]> in
https://savannah.nongnu.org/bugs/?40235
jas@kaka:~/dpkg/git2cl$
FWIW, this is a really nit-pick user experience bug report -- feel free
to close if it is hard to solve. The workaround is trivial:
git debpush --gbp --tag-only --upstream=upstream/3.0
/Simon
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: dgit
Source-Version: 17.0
Done: Ian Jackson <[email protected]>
We believe that the bug you reported is fixed in the latest version of
dgit, 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.
Ian Jackson <[email protected]> (supplier of updated dgit 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: SHA512
Format: 1.8
Date: Mon, 21 Sep 2026 00:16:30 +0100
Source: dgit
Architecture: source
Version: 17.0
Distribution: unstable
Urgency: medium
Maintainer: Debian tag2upload Delegates <[email protected]>
Changed-By: Ian Jackson <[email protected]>
Closes: 1105759 1143206
Changes:
dgit (17.0) unstable; urgency=medium
.
* Changed upstream tag selection algorithm:
New algorithm documented in git-deborig(1), with appropriate xrefs.
- Honour [export-orig] upstream-tag setting in debian/gbp.conf.
- Prefer upstream/ (or gbp-specified) tag if it exists.
Affects: git-debpush, git-deborig, git-debrebase, and dgit baredebian.
[Report from Simon Josefsson] Closes: #1105759.
.
git-debpush:
* Downgrade redundant quilt mode from check fail, to hint.
[Feedback from gregor herrmann, Colin Watson] Closes: #1143206.
* Distinguish lack of --branch from --branch=HEAD; --branch=HEAD is now
like any other --branch=TREEISH (and doesn't look at the working tree).
.
git-deborig calling convention changes:
* With --just-print, prefix tags with refs/tags/, for unambiuous output.
* Exit with bespoke status 6 for upstream tag resolution failure.
* git-deborig(1): Document the --just-print output format.
Checksums-Sha1:
7559b35accd9cf4c223a7509334b1bb6199dfbc6 2492 dgit_17.0.dsc
311e587d73fc73842820136dece844feb94be718 1071865 dgit_17.0.tar.gz
e65bccd68ba3f92914e4f3c304b3d3e79cefed0e 1376988 dgit_17.0.git.tar.xz
99fa2b83134ae4de15fdc0c32c999d77ab76cf11 17698 dgit_17.0_source.buildinfo
Checksums-Sha256:
b81c8cf49ace8f18e8cabc78294178d93be6a3faa1c770f99e0ab835542f88e0 2492
dgit_17.0.dsc
373b42b09edeb3b4255dad91c55f53427fc67127202b74c555aebe96bc5ed980 1071865
dgit_17.0.tar.gz
571fe17591210fce0e2e76691f58952d4e2c811d369dd937a6c153f7223641bf 1376988
dgit_17.0.git.tar.xz
50a4cbcf7283e0baa5b118de7d63d560e45690ddd0fc70eda71a90b63c04061c 17698
dgit_17.0_source.buildinfo
Files:
76f26617380453bdd484779cd966bcf7 2492 devel optional dgit_17.0.dsc
035ad8d81b31650b343b9fe51e4af703 1071865 devel optional dgit_17.0.tar.gz
a658f409ae50848aad713a3ad7175dd4 1376988 devel optional dgit_17.0.git.tar.xz
bf41fb7d6c51660772c96119b2fe8dc8 17698 devel optional
dgit_17.0_source.buildinfo
Git-Tag-Info: tag=03840527b70d636e5105a9c0d2f09c6bd6ee9c40
fp=41638114d132883b25a20ddd47515757d8002456
Git-Tag-Tagger: Ian Jackson <[email protected]>
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEN02M5NuW6cvUwJcqYG0ITkaDwHkFAmqwdaAACgkQYG0ITkaD
wHlKlA//TwHLhx0U1LlUcbAs2Jh3ep80+IYipULyFOvGopyx4uSgDNTOcaTkSo4r
6w+buOFcoWWcj4Ab/B0aLDWuI9ser4qRQyfwrUy1PpNxEjGR0Y/ySTKQPyaj6Mao
qCWuhDHS0fCa88OuDXpAa2Pc/bsgJ19mnaYg+WMJZZYWsqOaBPGGJSQIDqC/4oiR
1NISXOkUkLPsp8mYez8DQWEzz5RgeeC15kJ+804wFUfnLODvlersBz91CZkgyv05
qwnMEBEEZurXy3MTsNK+ZFOLyBNQKO4DQ2G92xmFhgBXGJ/S6XMNEerBgm3xbKoC
SnQZMTFiO3wgv2y4TtUyzXLYjH2X1Dv9f38jyXlswyqzyLe948tboWHFyXLQGR5m
oCSWbG85XlIvXq07M+lXEcJ3RE58aTQWGUz+pcpao7VWDcvqT1knC0fb7ZKTV3E0
Amo/ZbCiL+FcFyOPOLnPeyTZu+gOLcr9TAvhQ9K3oG7VRNXtOnU1KycY9FDPvbt2
TnzeneQc8+6CU2NsYLqTox7TT1VCjswu3yXU7mMxwkD14dV9wDvZ9a7f2nGBtN6a
qjXloLqhv6re8fHBLxXLeEVFptYoo3GzBaK9PyPWAFx7rLtnd0+ARTcqwnU7F5hK
GXJLduU5c5IF3r4TQQavLpPIlsQ+0QdFDgN4HQi0lPUepBfYCQ8=
=twYr
-----END PGP SIGNATURE-----
pgpi3Ur55Y4Xf.pgp
Description: PGP signature
--- End Message ---
