Merge lp:~sinzui/launchpad/publishbinary-without-publications into lp:launchpad
| Status: | Merged |
|---|---|
| Approved by: | j.c.sackett on 2012-11-15 |
| Approved revision: | no longer in the source branch. |
| Merged at revision: | 16277 |
| Proposed branch: | lp:~sinzui/launchpad/publishbinary-without-publications |
| Merge into: | lp:launchpad |
| Diff against target: |
50 lines (+21/-1) 2 files modified
lib/lp/soyuz/model/publishing.py (+6/-1) lib/lp/soyuz/tests/test_publishing.py (+15/-0) |
| To merge this branch: | bzr merge lp:~sinzui/launchpad/publishbinary-without-publications |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| j.c.sackett (community) | 2012-11-15 | Approve on 2012-11-15 | |
|
Review via email:
|
|||
Commit Message
Do not attempt to publish binaries for disabled DistroArchSeries.
Description of the Change
As seen in OOPS-0255df70569a8fcc9fe45c645713e04c,
PublishingSet.
publications to create. This mostly happens when an architecture is
newly disabled.
-------
RULES
Pre-
* PublishingSet.
binaries are for a disabled DistroArchSeries.
* The publishBinaries method is the only callsite for
expand_
architect
an architecture was used, but was later disabled.
QA
* Ask a webops to
* Visit https:/
* Disabled armel
* For qastaging,
* Verify the log does not container oopses
* Visit https:/
* Enabled armel again.
LINT
lib/
lib/
LoC
I have a 3,000 line credit this week.
TEST
./bin/test -vv -t TestPublishBinaries lp.soyuz.
IMPLEMENTATION
I updated expand_
I then updated publishBinaries() to return early if the expanded
binaries is empty.
lib/
lib/

Thanks, Curtis.