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.
FYI, there's an ancient bug for turning this on per-series, with a maybe-stale implementation. https://bugs.launchpad.net/launchpad/+bug/1016776 If I remember correctly I didn't push on it more because of the LoC policy that was in place at the time. Cheers, -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ]
signature.asc
Description: PGP signature
-- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
