always allow main archives to build on restricted architectures

Bug #600153 reported by Jelmer Vernooij
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
High
Jelmer Vernooij

Bug Description

Main archives should always be buildable on restricted architectures, even when there are no matching entries in archivearch.

In other words, for distro main archives enabled_restricted_architectures will always contain the same entries as ProcessorFamilySet.getRestricted().

Related branches

Jelmer Vernooij (jelmer)
Changed in soyuz:
status: New → Triaged
importance: Undecided → Medium
assignee: nobody → Jelmer Vernooij (jelmer)
Jelmer Vernooij (jelmer)
Changed in soyuz:
status: Triaged → In Progress
Revision history for this message
Ursula Junque (ursinha) wrote : Bug fixed by a commit
tags: added: qa-needstesting
Changed in soyuz:
status: In Progress → Fix Committed
Ursula Junque (ursinha)
Changed in soyuz:
milestone: none → 10.07
Revision history for this message
Julian Edwards (julian-edwards) wrote :

Just tried this on dogfood and no armel builds got created for an upload of "hello" until I inserted the main archive in archivearch.

tags: added: qa-bad
removed: qa-needstesting
Changed in soyuz:
milestone: 10.07 → 10.08
status: Fix Committed → Triaged
importance: Medium → High
Jelmer Vernooij (jelmer)
Changed in soyuz:
status: Triaged → In Progress
Revision history for this message
Launchpad QA Bot (lpqabot) wrote :
tags: added: qa-needstesting
removed: qa-bad
Changed in soyuz:
status: In Progress → Fix Committed
Jelmer Vernooij (jelmer)
tags: added: qa-ok
removed: qa-needstesting
Changed in soyuz:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers