Secondary classes need more safety checks
Bug #1517306 reported by
Robert Bruce Park
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bileto |
Triaged
|
Wishlist
|
Unassigned | ||
Bug Description
Just had a case where a dual silo contained qtmir and qtmir-gles, and during a build run all four packages were generated but only qtmir/vivid was rejected in the upload, due to the silo having a higher version than what was trying to be uploaded.
There already exists a check for this, but it only works for the primary (xenial) series in a silo. This check, and probably others, needs to be expanded to work with vivid half of dual silos also.
| Changed in cupstream2distro: | |
| assignee: | nobody → Robert Bruce Park (robru) |
| status: | New → Triaged |
Revision history for this message
| Robert Bruce Park (robru) wrote | #1 |
| Changed in cupstream2distro: | |
| importance: | Undecided → Wishlist |
| affects: | cupstream2distro → bileto |
| Changed in bileto: | |
| assignee: | Robert Bruce Park (robru) → nobody |
To post a comment you must log in.
Made some progress here: Secondary class is now overloading many fewer BuildBase methods with nops, so that should improve consistency of secondary packages (notably, diffs are now produced for vivid packages).
This issue of the version not being checked still exists though. Well, the version is checked at upload time, but probably the version should also be checked at collect time to ensure that the generated version number is high enough to get into the PPA at all.