populate-archive needs an option to specify virtualized
Bug #600640 reported by
Julian Edwards
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
High
|
Julian Edwards | ||
Bug Description
When creating copy archives, the available build architectures is affected by the initial virtualized state of the archive itself since you can't add architectures later (although this should also be fixed!). Right now, if I want to rebuild on armel, I can't because we only have non-virtual armel builders but the copy archive creation defaults to virtualized.
We need a --virtualized flag for populate-archive. (hey, it doesn't have enough options already right?)
Related branches
lp:~julian-edwards/launchpad/copy-archive-virtualization-bug-600640
- Jelmer Vernooij (community): Approve
-
Diff: 108 lines (+23/-9)2 files modifiedlib/lp/soyuz/scripts/populate_archive.py (+12/-3)
lib/lp/soyuz/scripts/tests/test_populatearchive.py (+11/-6)
| Changed in soyuz: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| assignee: | nobody → Julian Edwards (julian-edwards) |
| tags: | added: derivation |
Revision history for this message
| Ursula Junque (ursinha) wrote Bug fixed by a commit | #1 |
| Changed in soyuz: | |
| milestone: | none → 10.07 |
| tags: | added: qa-needstesting |
| Changed in soyuz: | |
| status: | Triaged → Fix Committed |
| tags: |
added: qa-ok removed: qa-needstesting |
| Changed in soyuz: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fixed in stable r11089 <http://