Binary uploads into the archive

[Daniel Leidert]

Hi,

by accident, I uploaded a binary package today (ruby-rouge) instead of
its source-package into the archive. I expected the binary package
being rejected once I discovered my mistake. But it was accepted
instead, and it was also not being rebuilt. Didn't we turn off binary
package uploads? Shouldn't this be rejected?

Regards, Daniel

[Andrey Rakhmatullin]

Post by Daniel Leidert
by accident, I uploaded a binary package today (ruby-rouge) instead of
its source-package into the archive. I expected the binary package
being rejected once I discovered my mistake. But it was accepted
instead, and it was also not being rebuilt. Didn't we turn off binary
package uploads? Shouldn't this be rejected?

We didn't, and they are still required for packages that need to go
through NEW. They are also the only way to bootstrap packages.

[Marco d'Itri]

I think what I should do is update the release number and do another (source
only) upload.

Correct: these uploads are supposed to be accepted because binary
uploads are still needed for passages in NEW (in that case: it's to
target experimental for the first upload of the pair).

[Sean Whitton]

Hello,

Post by Marco d'Itri

I think what I should do is update the release number and do another (source
only) upload.

Correct: these uploads are supposed to be accepted because binary
uploads are still needed for passages in NEW (in that case: it's to
target experimental for the first upload of the pair).

Also non-free packages that aren't marked as autobuildable.

[Mechtilde Stehmann]

Hello Dennis,

Post by Daniel Leidert
Hi,
by accident, I uploaded a binary package today (ruby-rouge) instead of
its source-package into the archive. I expected the binary package
being rejected once I discovered my mistake. But it was accepted
instead, and it was also not being rebuilt. Didn't we turn off binary
package uploads? Shouldn't this be rejected?

Coincidentally did the exact same thing (with igtf-policy-bundle); but
this is now stuck as it cannot migrate to testing (unless somebody
manually intervenes).
I think what I should do is update the release number and do another
(source only) upload.

You can do a new upload by increasing the revision number and an entry
in changelog that this is an source only upload.

Dennis

Regards
--
Mechtilde Stehmann
## Debian Developer
## PGP encryption welcome
## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F