Soyuz should not allow duplicated packages in NEW/UNAPPROVED queue
Bug #62976 reported by
Colin Watson
This bug affects 7 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
High
|
Unassigned | ||
pepess |
Invalid
|
Undecided
|
Unassigned |
Bug Description
It's still possible for two uploads with the same package name and version to land in the unapproved queue; furthermore it is then possible to simultaneously accept both of them. Neither of these should be allowed.
OOPS-2018FTPMASTERPUBLISH1
tags: | added: oops |
description: | updated |
Changed in launchpad: | |
status: | Triaged → New |
status: | New → Incomplete |
status: | Incomplete → Opinion |
status: | Opinion → Invalid |
status: | Invalid → Confirmed |
status: | Confirmed → In Progress |
status: | In Progress → Fix Committed |
status: | Fix Committed → Fix Released |
Changed in ubuntu: | |
status: | New → Incomplete |
status: | Incomplete → Opinion |
status: | Opinion → Invalid |
status: | Invalid → Confirmed |
status: | Confirmed → In Progress |
status: | In Progress → Fix Committed |
status: | Fix Committed → Fix Released |
Changed in ubuntu: | |
status: | Fix Released → New |
Changed in launchpad: | |
status: | Fix Released → Triaged |
no longer affects: | ubuntu |
Changed in launchpad: | |
status: | Triaged → Confirmed |
Changed in launchpad: | |
status: | Confirmed → Triaged |
Changed in launchpad: | |
status: | Triaged → New |
affects: | launchpad → google-launchpad-migrator |
Changed in google-launchpad-migrator: | |
assignee: | nobody → dexter dimaculangan (dexterjohn2011) |
status: | New → Confirmed |
affects: | google-launchpad-migrator → launchpad |
Changed in launchpad: | |
status: | Confirmed → Triaged |
assignee: | dexter dimaculangan (dexterjohn2011) → nobody |
information type: | Public → Public Security |
information type: | Public Security → Public |
Changed in launchpad: | |
status: | Triaged → Fix Released |
Changed in launchpad: | |
status: | Fix Released → Triaged |
Changed in launchpad: | |
status: | Triaged → Fix Released |
Changed in launchpad: | |
status: | Fix Released → Triaged |
no longer affects: | ubuntu |
Changed in launchpad: | |
status: | Triaged → Confirmed |
Changed in launchpad: | |
status: | Confirmed → Triaged |
Changed in launchpad: | |
assignee: | nobody → Anthony Ochoa (anthony1985) |
no longer affects: | ubuntu |
Changed in launchpad: | |
assignee: | Anthony Ochoa (anthony1985) → nobody |
Changed in launchpad: | |
assignee: | nobody → Wendell Nicolas (dentubuntu) |
Changed in launchpad: | |
assignee: | Wendell Nicolas (dentubuntu) → nobody |
Changed in launchpad: | |
assignee: | nobody → nguyen thanh anh vu (vunguyen67) |
assignee: | nguyen thanh anh vu (vunguyen67) → nobody |
Changed in launchpad: | |
status: | Triaged → Fix Released |
Changed in launchpad: | |
status: | Fix Released → Triaged |
Changed in launchpad: | |
assignee: | nobody → kirill (kirill-yalta) |
status: | Triaged → Confirmed |
no longer affects: | ubuntu |
Changed in launchpad: | |
assignee: | kirill (kirill-yalta) → nobody |
status: | Confirmed → Triaged |
Changed in launchpad: | |
assignee: | nobody → Jemiter Mwale (jemitermwale) |
Changed in pepess: | |
status: | New → Invalid |
Changed in launchpad: | |
assignee: | Jemiter Mwale (jemitermwale) → nobody |
information type: | Public → Private |
information type: | Private → Public |
Changed in launchpad: | |
importance: | Critical → High |
To post a comment you must log in.
That's unfortunatelly right ...
As we discussed on IRC, the fact we allow dups in NEW & UNAPPROVED is annoying, but the fix will require a fix in nascentupload workflow which we are trying to keep quiet until we land ArchiveRework (because the code will need redesign for PPA anyway).
My suggestion is to workaround this situation with two fixes:
* Materialize the state updates for each item inside the queue action batch, so the already existent lookup will find the just-modified candidate (this is a bug in previous implementation, one line fix)
* Fix queue "fetch" action to use ID as a tie-breaker when writing dupes to disk, so foo_1.0.dsc will become foo_1.0.dsc-<ID> if it is already in disk.
Kamion, would you be satisfied (for a while) with this alternative plan ?