XPost: linux.debian.devel, linux.debian.policy   
   From: cjwatson@debian.org   
      
   On Wed, Feb 11, 2026 at 01:59:10PM +0100, Simon Josefsson wrote:   
   >Holger Levsen  writes:   
   >> "Uploads to NEW (even if only binary-NEW), because for those ftp.d.o   
   >> currently demands maintainer-generated binaries."   
   >   
   >Why on earth are we accepting maintainer-generated binaries into the   
   >archive in 2026?   
   >   
   >Yes, I know several reasonable answers to that question, but they don't   
   >resolve the concern with maintainer-generated binaries.   
   >   
   >NEW uploads should be permitted to be source-only.   
      
   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.)   
      
   --   
   Colin Watson (he/him)                              [cjwatson@debian.org]   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)