Merge lp:~jelmer/launchpad/600153-qafix into lp:launchpad
| Status: | Merged |
|---|---|
| Approved by: | Brad Crittenden on 2010-07-27 |
| Approved revision: | no longer in the source branch. |
| Merged at revision: | 11239 |
| Proposed branch: | lp:~jelmer/launchpad/600153-qafix |
| Merge into: | lp:launchpad |
| Diff against target: |
54 lines (+5/-8) 2 files modified
lib/lp/soyuz/model/archive.py (+3/-4) lib/lp/soyuz/model/publishing.py (+2/-4) |
| To merge this branch: | bzr merge lp:~jelmer/launchpad/600153-qafix |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Brad Crittenden (community) | code | 2010-07-23 | Approve on 2010-07-27 |
| Launchpad code reviewers from Canonical | code | 2010-07-27 | Pending |
|
Review via email:
|
|||
Description of the Change
This fixes the qa-badness of bug 600153. process-upload was manually looking at ArchiveArch to determine what restricted architectures the archive could build on rather than checking Archive.
| Jelmer Vernooij (jelmer) wrote : | # |
Hi Brad,
Thanks for the review.
Since this really is a layering issue (the original code was skipping a layer and looking at the raw data directly, but doing a bad job interpreting that data), I'm not sure if it would make sense to add a test. I don't want to put too much knowledge about how we determine what restricted architecture families are allowed into the publisher tests - that logic is already covered in the archive tests.
What do you think?

Hi Jelmer,
Please sort your import items alphabetically.
Based on the QA report this change looks good (though I can't claim deep enough knowledge to know for sure).
You didn't add or modify any tests for this change. Is this fix not testable? Would an appropriate test on the original branch have avoided the second round?