Holger Levsen writes ("Bug#1127616: developers-reference: should document using
git-debpush to upload [and 1 more messages]"):
> On Tue, Feb 10, 2026 at 06:12:26PM +0000, Ian Jackson wrote:
> > > How about a patch that recommends use of dgit for uploads?
> > Holger, in amongst all the heat here, you seem to have missed this
> > question.
>
> indeed.
>
> I guess in general this depends on the patch and the kind of recommendation
> (eg "must use!" vs "should give a try"...)
Thanks for the reply.
> (TBH currently I'm a bit sceptical that such a patch would also be too
> enthusiastic. That said, please do provide a bug with patch or an MR and
> we can then discuss it on its actual merrit. An MR would actually be
> preferred by me over a bug, but whatever works.
I can prepare an MR, sure.
> Also I'm really also not convinced yet that we/dev-ref should recommend dgit
> for everyone and everthing right now. I do think it definitly should be
> mentioned and then maybe/probably become recommended later.
> )
I think dgit should be the recommended approach whenever the packaging
work is done in git in a dgit-compatible format. This means almost
all git workflows commonly used in Debian except for the
language-specific package manager monorepos (eg Rust and Haskell).
dgit is extremely mature by now. All the functionality I would be
recommending has existed since at least 2018, with only bugfixes and
UX improvements since then. It has been very stable, and had almost
no changes[1] in the trixie release cycle (ie for several years now).
We are not talking about some hare-brained innovation here. It really
does (i) make uploading easier (ii) catch more mistakes and anomalies
(iii) produce better output for users and downstreads.
Thanks,
Ian.
[1] dgit.deb and the dgit program have had new features added to
support tag2upload, but that's largely new code which isn't used by
the normal "dgit push" flow. The codepaths I'd be recommending are
all very well tested by the dgit test suite and by daily use by dgit
users.
--
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.
