Johannes Schauer writes ("Bug#801435: closed by Ian Jackson
<[email protected]> (Bug#801435: fixed in dgit 5.7)"):
> Quoting Debian Bug Tracking System (2018-07-05 16:30:04)
> > * dgit: Check that entirely-new uploads to Debian are not
> > source-only-uploads, as those are REJECTed. Closes:#801435.
>
> I didn't investigate further, but this sounds as if dgit only takes care that
> one cannot do a source-only upload for entirely new packages. But my initial
> message was talking about uploads with new binary packages that have to first
> go to binary-NEW.
>
> Thus, maybe this bug is actually not fixed by this version?
Arguably you are right. The problem is that detecting binary-NEW is
not anywhere near as easy as detecting source-NEW.
I think in principle it may be possible, but it would involve dgit
parsing your debian/control to extract the list of binary packages
(which I think is required to be accurate in Debian?) and correlating
it with the archive. If you think that would be valuable then please
say and I will clone this bug. I'm afraid it won't get done any time
soon though...
Ian.
--
Ian Jackson <[email protected]> These opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
