Your message dated Sun, 08 Mar 2026 18:20:25 +0000
with message-id <[email protected]>
and subject line Bug#990667: fixed in dgit 14.11
has caused the Debian Bug report #990667,
regarding dgit(7) Documentation: MODEL dgit-repo, --overwrite, /fast
forward/fast-forward/, --deliberately-not-fast-forward, ...
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.)
--
990667: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990667
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dgit
Version: 9.13
Severity: wishlist
This is a wishlist bug report on dgit(7) and dgit(1) documentation.
dgit is a very useful tool which I think all Debian actively maintained
packages eventually need to migrate to. But dgit suffers fear,
self-imposed uncertainty, and doubt feelings from well-intended DDs
since it does many irreversible things such as uploading
(source-)packages with very scant explanation of its design and
functioning principles in its documents. For example, the documentation
of dgit encourages to use "--overwrite" to make dgit to behave in
non-default way without mentioning possible adverse effects explicitly.
As I read https://bugs.debian.org/913451, it looks quite complicated due
to the task dealing is complicated. ( ... still, I am not sure exactly
how this impacts us). The word like "overwrite" is scary for publicly
published git contents. Another scary thing is
"deliberately-not-fast-forward".
I think dgit(7), especially around "MODEL" needs more love.
* What exactly is dgit-repo?
* Is this URL printed by dgit print-dgit-repos-server-source-url?
git+ssh://[email protected]/dgit/debian/repos/_dgit-repos-server.git
or repo like:
https://git.dgit.debian.org/dgit (for dgit)
or
https://salsa.debian.org/dgit-team/dgit.git (for dgit)
* What is the role separation between the "package VCS site" and
dgit-repo? I mean "package VCS site" such as:
Vcs-Git: https://salsa.debian.org/dgit-team/dgit.git
* Where do operation such as "dgit push" and "dgit push-source" send
data to?
* dgit-repo (?, one got from dgit clone had following refs)
- vcs-git (looks like normal branch tracking Vcs-Git repo)
- dgit (gitk works but "git ls-remote" doesn't work)
* Vcs-Git git repo accessed by git
- origin (has archive/... tags but no dgit like branch)
* Debian archive (incoming)
* Usage of words: "repo" and "archive", within dgit context may be
documented clearly somewhere.
* Why some dgit documents use "fast forward" without hyphen and some
dgit documents use "fast-forward" with hyphen. (It looks like
git-merge(1) consistently uses "fast-forward" with hyphen.) Are they
used in the same sense as used by git-merge(1)? If so, it may be
better to mention it. Please also explain
--deliberately-not-fast-forward.
* In --overwrite section in dgit(1) doesn't mention
--deliberately-not-fast-forward. The --overwrite seems to me for the
*first* time for each suite but "not the very first upload with dgit".
This latter fact needs to be documented clearly. Anyway, these 2
things may scare new users.
* In MODEL, in the following text, "used" is very confusing:
dgit maintains a pseudo-remote called dgit, with one branch per
suite. This remote cannot be used with plain git.
At least, gitk can be used to identify their existence. I see git remote
branch like remotes/dgit/dgit/sid in gitk for the local repository which
used dgit but "git ls-remote" etc. doesn't seem to work. I don't see
definition what exactly is the *pseudo-remote* in MODEL. I don't know
exactly but something like:
dgit pseudo-remote commit is like a git commit refs but without
the actual file content in the git repository. Actual file
content needs to be obtained by dgit. (or whatever it actually
does, please describe.)
dgit maintains a pseudo-remote called dgit, with one branch per
suite. The existence of such branch ad associated tags can be
seen by gitk ... but cannot be used with plain git since it is
missing some normal git file content. The content of ....
archive ....
The mastery of pseudo-remote and its persistence over --overwrite gives
me iffy feeling.
The good news is dgit stops if try to do something stupid.
Thanks and regards
Osamu
-- System Information:
Debian Release: 11.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-7-amd64 (SMP w/12 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages dgit depends on:
ii apt 2.2.4
ii ca-certificates 20210119
ii coreutils 8.32-4+b1
ii curl 7.74.0-1.3
ii devscripts 2.21.2
ii dpkg-dev 1.20.9
ii dput 1.1.0
ii git [git-core] 1:2.30.2-1
ii git-buildpackage 0.9.22
ii libdpkg-perl 1.20.9
ii libjson-perl 4.03000-1
ii liblist-moreutils-perl 0.430-2
ii liblocale-gettext-perl 1.07-4+b1
ii libtext-csv-perl 2.00-1
ii libtext-glob-perl 0.11-1
ii libtext-iconv-perl 1.7-7+b1
ii libwww-curl-perl 4.17-7+b1
ii perl [libdigest-sha-perl] 5.32.1-4
Versions of packages dgit recommends:
ii distro-info-data 0.50
ii liburi-perl 5.08-1
ii openssh-client [ssh-client] 1:8.4p1-5
Versions of packages dgit suggests:
ii sbuild 0.81.2
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: dgit
Source-Version: 14.11
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: Sun, 08 Mar 2026 17:06:24 +0000
Source: dgit
Architecture: source
Version: 14.11
Distribution: unstable
Urgency: medium
Maintainer: Debian tag2upload Delegates <[email protected]>
Changed-By: Ian Jackson <[email protected]>
Closes: 990667 1126152 1127470 1127618 1127666 1128591
Changes:
dgit (14.11) unstable; urgency=medium
.
tag2upload improvements:
* git-debpush: Support --deliberately in git-debpush. Closes: #1127470.
* git-debpush, dgit: Provide --untaint-history convenience alias for
--deliberately-include-questionable-history. As per #1127470.
* Generate our own Message-IDs on the Oracle, and convey them to the
Manager via o2m protocol 9. Closes: #1127618.
[Reviews and fixes from Sean Whitton]
.
Bugfixes:
* tag2upload: Don't sometimes send emails with wrong status in Subject.
* tag2upload: Do not include inapplicable retry advice in email reports.
* dgit/tag2upload overwrite checks: Do not refer inaccurately to the archive.
* dgit/tag2upload: Avoid crashing on some fatal errors due eg to
unfinalised changelogs. Closes: #1126152.
* dgit rpush: Do print applicable retry advice on early failures.
.
Documentation:
* Completely overhaul docs of --deliberately, and error messages.
New section in dgit(7) describing tainted history.
Closes: #990667, #1127666. [Reports from Osamu Aoki & Simon Josefsson]
* dgit(1): Expand xrefs. Closes: #1128591. [Report from Simon Josefsson]
* git-debrebase(1): Document --noop-ok for scrap, make-patches.
Promptted by #1129577. [Report from Charlemagne Lasse]
Checksums-Sha1:
a4a788da487e486c2b413d2ab5a53bf11c0f1c21 2522 dgit_14.11.dsc
7fced3f521c1ccc352ec7a68efce5a44bfee4031 1033732 dgit_14.11.tar.gz
d5bfe73ca3ab5541788f54e364fdc0369c8617be 1331552 dgit_14.11.git.tar.xz
5f805fcaddf3fce761a2d6d37c1c5e34b783a970 17276 dgit_14.11_source.buildinfo
Checksums-Sha256:
88cd447ededba7810b3dceb161a7f772a55ed687a0c67881c32ed7f5c8902bbd 2522
dgit_14.11.dsc
928b8260eb2d433fdd86f78a56d15f5ed804a27e75022c978f81b2c02f3aab6a 1033732
dgit_14.11.tar.gz
d8998055e1f01ef3af2f65fe7f102011ec43fac8939f01446f5dd1e66e859a36 1331552
dgit_14.11.git.tar.xz
5859a79e3b2d7ec7fefa57da49fabc0b88dada668909d2d110e147a581f3c673 17276
dgit_14.11_source.buildinfo
Files:
294e92e76859e1894207ed4b3e6ec6c5 2522 devel optional dgit_14.11.dsc
4097ab42df68f80c183222106e547373 1033732 devel optional dgit_14.11.tar.gz
3551fd85670b27dee812f2fafeebe70f 1331552 devel optional dgit_14.11.git.tar.xz
51932d04bc1e03952f3e0dcfbf099791 17276 devel optional
dgit_14.11_source.buildinfo
Git-Tag-Info: tag=2a01b35e50dae059940e2fe999a1d7b99d143ed5
fp=41638114d132883b25a20ddd47515757d8002456
Git-Tag-Tagger: Ian Jackson <[email protected]>
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEN02M5NuW6cvUwJcqYG0ITkaDwHkFAmmtuj4ACgkQYG0ITkaD
wHlkKA//bHl86FfKTQiszff5VCOByW7c10zIV+WGLo5ab6lm4N+MKlGg7gGKgNkL
St7RXQVmi814huf1Avd/SJjo4VswecmOqUREOc41AISX2WavxOqVQXhIq0+hNfac
FaWqu4VYrGRWmy/lmjlpUWWlRh6wmwFldNn3s9cwEc3BxLwnFSsloJPm0bPgS8hD
J0nP53PSU3RNfO4Sf8VuMTT7Niy4K8Pfk6G40kNiJ8h85AwmXt1nigiCJCwLVdAh
mykGLJ73PhXPoQVHcxmVr9Afw1TsQAtnOyNnV2yZ1ZCFcCeic7UZt4hkHuk4AiW1
vOvXVTaIkSsCbWxv2Fq620DmPjaFRlpOGCLla+vBb1ZvlPrnD2SJEs3JzmtLyR4v
4b+rV8ocms2xuE8U8Bh94OBV2NeAeDGBJNXMMBJDI8pEyM/C0tLFkfutSYc3WaSa
nWT683Mmn3X0b3+hvm4J0QoUyZCMQIgOinOP/R9HDO0Pib0IzEhvZtsiYiZ09jgx
deqsuc3yRCMK+hrzkCFUDKsQ5TA91soj+GBEQgrVP5zkurCiYxWRGXl9/nh0ftXq
y1EDNhcVIoH626dPr/qnICkp9QrkUaiVxonXPPDBMHT4q8pLex2LhXt/jtRWLNkA
GVwmmmyM/c0WiZham///pmXLs3iT4leZg8CRDqDmd1C4m3sd3Kw=
=THWq
-----END PGP SIGNATURE-----
pgpRsQQdyUN8g.pgp
Description: PGP signature
--- End Message ---
