Architectures should be able to be disabled

Bug #633139 reported by Julian Edwards
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Julian Edwards

Bug Description

Sometimes, after a new distro release is opened, it can be decided not to support certain architectures any more. This can be worked around by removing the chroot for the distroarchseries to prevent new builds being created, but it does not stop the publisher from publishing arch-all builds in the indexes for the arches concerned.

A better approach is to put a switch on the distroarchseries to deactivate it. This would prevent builds and anything from being published to it.

Related branches

Changed in soyuz:
status: New → Triaged
importance: Undecided → High
assignee: nobody → Julian Edwards (julian-edwards)
tags: added: soyuz-core soyuz-publisher
Revision history for this message
Launchpad QA Bot (lpqabot) wrote : Incremental fix
Changed in soyuz:
milestone: none → 10.10
status: Triaged → In Progress
Ursula Junque (ursinha)
tags: added: qa-untestable
tags: added: qa-needstesting
removed: qa-untestable
tags: added: qa-ok
removed: qa-needstesting
Changed in soyuz:
status: In Progress → Fix Committed
Revision history for this message
Launchpad QA Bot (lpqabot) wrote : Bug fixed by a commit
tags: added: qa-needstesting
removed: qa-ok
tags: added: qa-ok
removed: qa-needstesting
Revision history for this message
Robert Collins (lifeless) wrote :

The tip of production-stable has the makefile check for db schema changes disabled; Julian, can you please land another branch reenabling that check (which is ok now because the late-arriving patch is now in the tree) so that we have protection from other branches. Thanks.

Revision history for this message
Julian Edwards (julian-edwards) wrote : Re: [Bug 633139] Re: Architectures should be able to be disabled

On Wednesday 15 September 2010 21:54:07 you wrote:
> The tip of production-stable has the makefile check for db schema
> changes disabled; Julian, can you please land another branch reenabling
> that check (which is ok now because the late-arriving patch is now in
> the tree) so that we have protection from other branches. Thanks.

Yes I'm aware of that thanks.

Curtis Hovey (sinzui)
Changed in soyuz:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.