Your message dated Fri, 31 Jul 2026 12:20:51 +0000
with message-id <[email protected]>
and subject line Bug#1142508: fixed in dgit 16.1
has caused the Debian Bug report #1142508,
regarding git-debpush(1) manpage improvements
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.)
--
1142508: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1142508
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: git-debpush
Version: 16.1~exp1
gregor herrmann writes ("Bug#1106071: closed by Debian FTP Masters
<[email protected]> (reply to Ian Jackson
<[email protected]>) (Bug#1106071: fixed in dgit 16.1~exp1)"):
> I just made my first upload of a -1 package with git-debpush 16.1~exp1
> with the pristine-tar support. [0]
Hi. I suppose I should have guessed that someone would see the BTS
traffic and try it out :-). There are still some minor rough edges to
sort out before a public announcement (which I'll make on d-d-a),
notably the large number of harmless warnigns in the email report.
> - I didn't know (or find out by reading the manpage) if I need to do
> anything or if the pristine-tar branch is just used when it's there
> or something else. In the end I just typed `git debpush' and read in
> the mailed log, that pristine-tar was used. Yay.
> A bit of explanation in the manpage might be nice.
Yes, it's basically magical. If your local pristine-tar branch has
data for the version you're uploading, it is used. There are
downstream checks that would detect and prevent usage of tarballs that
don't match your HEAD, so this is not as risky as it sounds.
I agree some of this should be documented. It would fit into
git-debpush(1) I think. The docs ought also to state what the inputs
are. In particular, it is a (soft) principle of git-debpush that it
only uses locally available information to generate the tag. Remote
information is only used to check that you're not making a mistake.
So probably there should be a "what does this command do" section.
> - There's one part in the POD which might need an update: the
> "pristine-tar" item in the --force documentation:
>
> https://salsa.debian.org/dgit-team/dgit/-/blob/experimental/git-debpush.1.pod?ref_type=heads#L317
Ah yes.
> (Side note, as I was `locate'ing through my disk: I have 5 local
> repos which have a .git/git-debpush/ direcory. Not sure what this is
> (maybe aborted uploads?) but if I had more than 5 of them on my disk
> I might be unhappy :))
These are harmless. got-debpush prefers using that for temporary
working areas, rather than /tmp. /tmp is very bad for lots of
reasons. If things succeed, it will normally delete it again. On
failure, it's deliberately left behind for diangosis.
This should be documented in FILES in git-debpush(1).
Ian.
--
Ian Jackson <[email protected]> These opinions are my own.
Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.
--- End Message ---
--- Begin Message ---
Source: dgit
Source-Version: 16.1
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: Fri, 31 Jul 2026 12:18:04 +0100
Source: dgit
Architecture: source
Version: 16.1
Distribution: unstable
Urgency: medium
Maintainer: Debian tag2upload Delegates <[email protected]>
Changed-By: Ian Jackson <[email protected]>
Closes: 1106071 1142508
Changes:
dgit (16.1) unstable; urgency=medium
.
git-debpush:
* git-debpush(1): New FILES and BEHAVIOUR sections;
remove mention of no-longer-relevant --force-pristine-tar.
[Report from gregor herrmann] Closes: #1142508.
.
dgit (16.1~exp1) experimental; urgency=medium
.
git-debpush:
* Implement pristine-tar support. Closes: #1106071.
Checksums-Sha1:
dd4bb10d0956b92c1b1886fb1e7c1345d4b8d664 2528 dgit_16.1.dsc
fea28353669b4383fe1daa5a779b7e67010dcaaa 1066226 dgit_16.1.tar.gz
d0cafd4f90cdd6dda5e0beaac5f980a31ef28f18 1368888 dgit_16.1.git.tar.xz
471722389294b99be694f5acc6db9b0055f9ae57 17522 dgit_16.1_source.buildinfo
Checksums-Sha256:
d7aeadbe6513f78ee4fa1c3e267793c8cf3299221f92a2ed0b98742024dba2f0 2528
dgit_16.1.dsc
2d71313e6ca9feeb1dd4965656a7cf7a0ff0ede62955075876a0c608170488ad 1066226
dgit_16.1.tar.gz
fab85d4e2bd723a87fb12f35495b4a9379d018bc255cffa3379b49aaf09178dd 1368888
dgit_16.1.git.tar.xz
afe7f1ce0404dff0abbd34ac50a5be688ea6cbe4f6e6174bcae2dc86c8cada10 17522
dgit_16.1_source.buildinfo
Files:
1ba8b9791b153d58eb168f896ce02f1d 2528 devel optional dgit_16.1.dsc
d5670e66f8538a8f22192b2c657b3bc5 1066226 devel optional dgit_16.1.tar.gz
cf3499eb07348f94b2c3d84f71a7cc6b 1368888 devel optional dgit_16.1.git.tar.xz
4b73e247dca895560744b63d71f0b7df 17522 devel optional
dgit_16.1_source.buildinfo
Git-Tag-Info: tag=04d71a5360b5c3962660abacbf4da09ba88d049e
fp=41638114d132883b25a20ddd47515757d8002456
Git-Tag-Tagger: Ian Jackson <[email protected]>
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEN02M5NuW6cvUwJcqYG0ITkaDwHkFAmpskJAACgkQYG0ITkaD
wHngBg//ZveQQmZGbu9VS1uAnC1vjvilW1tBrkzrl3hAtsMdS7G+Tsd3X9TP8Aii
BTsC/fAIp2Hb809p9heD2hmq0yVFkSBOB1sg7wvOnqr4Jm+x6Mp9BHZdoLUThQT9
7L1Sa7s6NFScWQw5iH/ODSXKnc1+7CSsbcx5PmMsAUQ+alIrFPoHh+9eiLBwqxvt
5HG4cpGXTFXlDxddRCViNL1WG0c/3QnVXlHUQF0eHBNH+piK8EMqFxi4eztk3eKt
KpVK9VKefapRdBL9+Iv4DzTnMc7xca1m1kwcRjyUnE49EMru6d3OPOFu1Q39hOxU
aftxRgI69VL/52+6zdu2WDxWiccqpXaGFnln2rqN0jIWlbs1eYgZr4ZQH8vIc6as
jfS6EIohnCbQQYh/nUUn4iZ/UgOIJPTfBovyxCKfuUWm0F2q9WvYnVcnhav36p5q
/Rwf26hK0dlpxUBuFTzSte/YyQvcefvG9V1gQCf33MHZy7fIkPQKTp0yczpP26bZ
sxhyF+WG5m8caT/jBp5aD6ndY8DBbnW965p1gwODIWtfusV/wzFnNzJzXheKbkCG
P2sOBaFb6KBmgmtzNgazKqNgN++09rry6AFXokFcbCn5dmU4v86Flwuz0yztYLbY
7AvaNH6LfW3UKvGZbFVR82wBVP8upWY7sZGgc+iH6vv7wi3IwpU=
=OcJG
-----END PGP SIGNATURE-----
pgpU4zQF1G758.pgp
Description: PGP signature
--- End Message ---
