followup uploads are rejected after NEW processing
Bug #33974 reported by
Matthias Klose
This bug report is a duplicate of:
Bug #31760: Check presence of orig in NEW/ACCEPTED/UNAPPROVE queue.
Edit
Remove
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
I.e. last seen with python-pullparser.
- source is in NEW, gets processed
- ack message is sent
- another upload is made, without .orig.tar.gz,
which is rejected (no .orig.tar.gz)
either the Rejected message could be more accurate, or soyuz could delay the upload, until the source is visible in it's database.
Revision history for this message
| Celso Providelo (cprov) wrote | #1 |
Revision history for this message
| Celso Providelo (cprov) wrote | #2 |
| Changed in soyuz: | |
| assignee: | nobody → cprov |
| status: | Unconfirmed → Confirmed |
| Changed in soyuz: | |
| assignee: | Celso Providelo (cprov) → nobody |
To post a comment you must log in.
Good description, yes, it's expected, we do not inspect the NEW queue looking for files (.orig).
I wonder if we should do it, since we ae relying in something not ACCEPTED to ACCEPT another one, in the case we have an homogeneous workflow.
Maybe we should inspect the NEW queue and if the current upload requires that information we keep it as NEW too. It also implies in some cases that the previous source doesn't even need to be build and can be published directly as SUPERSEDED.
Looks like we need to discuss it more accuratelly.