Comment 8 for bug 1016776

Hi Iain,

I had missed the discussion of this on ubuntu-release, because I didn't realize from the bug title that this was about -proposed for the devel release.

I'm concerned that such a setting for the ${devel}-proposed pocket actively contradicts the purpose of -proposed for devel releases - namely, that it exists *only* for the purpose of ensuring archive consistency, and therefore is only meant to be used for build environments, where we *do* want automatic upgrades to the packages available.

Therefore, from what I can see, users should have -proposed disabled entirely on upgrade to the development series, because they should never be installing packages from -proposed; and build environments which do have -proposed enabled should most definitely get upgrades automatically from -proposed.

How are you expecting this to work for $devel-proposed, as enabled on the launchpad buildds?