The proposal to merge lp:~wgrant/launchpad/bug-897999 into lp:launchpad has 
been updated.

Description changed to:

Presently a main archive (primary or partner) that builds on non-virtual 
builders is implicitly allowed to use all restricted processor families, 
regardless of the configuration in the database. The widgets on Archive:+admin 
and Distribution:+edit attempt to enforce this, but end up being both too 
strict and too lenient, resulting in problems like bug #897999.

This branch removes the main archive special case. It applies to a total of two 
archives on production which can be easily configured manually, it's a fair bit 
of code, and the corresponding UI has always been fairly broken. All archives 
can now have restricted families enabled or disabled as desired.

Ubuntu's primary and partner archives will need tweaking on production before 
this is deployed; I suspect that simply clicking Save on their respective 
+admin forms will be sufficient.

For more details, see:
https://code.launchpad.net/~wgrant/launchpad/bug-897999/+merge/125640
-- 
https://code.launchpad.net/~wgrant/launchpad/bug-897999/+merge/125640
Your team Launchpad code reviewers is requested to review the proposed merge of 
lp:~wgrant/launchpad/bug-897999 into lp:launchpad.

_______________________________________________
Mailing list: https://launchpad.net/~launchpad-reviewers
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~launchpad-reviewers
More help   : https://help.launchpad.net/ListHelp

Reply via email to