Merge lp:~michael.nelson/launchpad/529926-partner-override-to-main into lp:launchpad
Status: | Merged |
---|---|
Approved by: | Michael Nelson |
Approved revision: | no longer in the source branch. |
Merged at revision: | not available |
Proposed branch: | lp:~michael.nelson/launchpad/529926-partner-override-to-main |
Merge into: | lp:launchpad |
Diff against target: |
129 lines (+52/-10) 4 files modified
lib/lp/soyuz/doc/distroseriesqueue.txt (+1/-1) lib/lp/soyuz/model/queue.py (+9/-4) lib/lp/soyuz/scripts/queue.py (+9/-5) lib/lp/soyuz/tests/test_packageupload.py (+33/-0) |
To merge this branch: | bzr merge lp:~michael.nelson/launchpad/529926-partner-override-to-main |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Paul Hummer (community) | code | Approve | |
Brad Crittenden (community) | Needs Information | ||
Review via email: mp+21329@code.launchpad.net |
Commit message
Uploads that are overridden to a component requiring a different archive will be published in the correct archive context.
Description of the change
Fixes bug 529926 by ensuring that when the component of a source package upload is overridden, the target archive of the upload is also overridden as necessary.
This only becomes apparent when a "main" archive is uploaded and overridden to "partner" (or debug, I assume, any component that has a separate archive). In this case the source package release was being overridden correctly, but it is the package upload's archive that is used to create the new publishings.
Pre-implementation notes on the bug, and I chatted with Julian about this as well.
I was originally planning simply to use the SourcePackageRe
To test:
bin/test -vv -m lp.archiveuploader
Michael can you resolve the conflicts in your branch? I gave it a try but failed.