component of new binary packages should default to source component
Bug #192076 reported by
Martin Pitt
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
Critical
|
Ian Booth | ||
Bug Description
Doing binary NEW is much more work and error prone than it needs to be. In 99% of the cases the binaries go to the same component as the source.
As it is now, they all default to 'main'. Thus we override most packages to universe. Sometimes this means we put binaries of multiverse sources into universe, because we overlooked this (and explicitly checking for the component of the source takes a lot of time, too).
Unless the binary has an explicit component in its Section:, it should default to the source package component.
Related branches
lp:~wallyworld/launchpad/package-defaults-192076
- Steve Kowalik (community): Approve (code)
-
Diff: 195 lines (+90/-18)3 files modifiedlib/lp/archiveuploader/nascentupload.py (+20/-4)
lib/lp/archiveuploader/nascentuploadfile.py (+23/-12)
lib/lp/archiveuploader/tests/test_uploadprocessor.py (+47/-2)
| Changed in soyuz: | |
| importance: | Undecided → Medium |
| milestone: | none → 1.2.3 |
| status: | New → Triaged |
| Changed in soyuz: | |
| milestone: | 1.2.3 → 1.2.4 |
| milestone: | 1.2.4 → none |
Revision history for this message
| Adam Conrad (adconrad) wrote | #1 |
Revision history for this message
| Colin Watson (cjwatson) wrote | #2 |
| Changed in launchpad: | |
| importance: | Medium → Low |
Revision history for this message
| Francis J. Lacoste (flacoste) wrote | #3 |
| Changed in launchpad: | |
| importance: | Low → Critical |
| Changed in launchpad: | |
| assignee: | nobody → Ian Booth (wallyworld) |
| status: | Triaged → In Progress |
| tags: | added: escalated |
| tags: | removed: escalated |
| tags: | added: escalated |
Revision history for this message
| Launchpad QA Bot (lpqabot) wrote | #4 |
| tags: | added: qa-needstesting |
| Changed in launchpad: | |
| status: | In Progress → Fix Committed |
| tags: |
added: qa-ok removed: qa-needstesting |
| Changed in launchpad: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
This bug is still rather problematic for archive admin tasks. All new binaries now default to universe, but for large/complex packages like the kernel (source package: linux), we want most of the binaries in main, but a few scattered elsewhere.
The linux control files are correct (lists some packages in universe, most in main), but since all the packages land in universe, overriding them by hand to be correct is difficult.
To reiterate this bug's request, and flesh out the exact behaviour we'd like to see:
1) All NEW source packages should go to universe if no component is listed, to multiverse if the component is "non-free", and should go to the specified component (universe, multiverse, restricted) if explicitely stated.
2) All NEW binary packages should default to the component of the parent source package, unless explicitely overridden, again overriding "non-free" to "multiverse" (so, a source in main that produces binaries in main and universe should get default overrides that DTRT, a source in multiverse should get all binaries in multiverse, etc)