(reordering slightly)
Colin Watson writes ("Bug#1127616: developers-reference: should document using
git-debpush to upload"):
> On Wed, Feb 11, 2026 at 01:59:10PM +0100, Simon Josefsson wrote:
> >Why on earth are we accepting maintainer-generated binaries into the
> >archive in 2026?
>
> Just to be clear, I think this is a misinterpretation of the current
> state. https://wiki.debian.org/ThrowAwayNewBinaries is implemented; we
> still require maintainer-generated binaries in that workflow so that the
> DFSG team can review the resulting layout, but that doesn't equate to
> "accepting maintainer-generated binaries into the archive" as part of
> the typical NEW workflow.
>
> (Yes, there are other situations in which maintainer-generated binaries
> do get into unstable, although not testing, and non-main is still an
> issue. But let's not conflate that with what normally happens when NEW
> is involved.)
This all matches my understanding. Nevertheless:
> NEW uploads should be permitted to be source-only.
This would be a significant improvement. I think binaries needed for
review by the DFSG team should be autobuilt.
For one thing that would mean we would have additional confidence that
the binaries being reivewed match what the source code will produce in
the future, after the package is accepted. It would also relieve the
uploader of a good deal of palaver.
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.
