On Thu, Oct 20, 2016 at 09:58:45AM +0000, Adam Conrad wrote: > On Wed, Oct 19, 2016 at 06:02:35PM -0700, Steve Langasek wrote:
> > The only complication I'm aware of is that we absolutely must have different > > apt preferences behavior for chroots - such as buildd chroots - than for end > > user systems; but that should be solvable by using a preferences.d file > > shipped in the right package. Probably either software-properties-common or > > ubuntu-release-upgrader-core? > That's backwards. If you want the default to be safe, and the exception > to be the wild west, we should configure it *just* like backports. > NotAutomatic on the server side, no surprises for people without the right > apt preferences bits in place. > The buildd chroots already carry a pin for backports to reverse the effect > of NotAutomatic, and could as easily do so for proposed, if there was > consensus that this behaviour change is the Way and the Light. The reason I thought of doing it this way around is that I have existing chroots where I enable -proposed (for the obvious reasons), and it would be convenient for me to not have to touch them to add this apt config manually; I assume there will be other developers in the same boat. But if there's a preference to change this on the archive side to make the pocket NotAutomatic and then adjust the buildd chroots, I can live with that. I'd just like us to fix it so it's sensible behavior for end users by default. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ [email protected] [email protected]
signature.asc
Description: PGP signature
-- Ubuntu-release mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
