On Wednesday, July 10, 2013 11:36:58 PM Dave Walker wrote:
> On 10 July 2013 20:41, Robert Park <robert.park@canonical.com> wrote:
> > On Sun, Jul 7, 2013 at 12:31 PM, Jo-Erlend Schinstad
> >
> > <joerlend.schinstad@gmail.com> wrote:
> >> Perhaps it would be wise to disable the option in the GUI with a proper
> >> explanation of this? It's obvious that proposed _might_ break things, but
> >> it's certainly not obvious that it's not intended for humans when there's
> >> a
> >> GUI to enable it.
> >
> > The issue is that it's only in the *devel* pre-release when it's not safe
> > for humans to enable it. The GUI for enabling it needs to exist because
> > there are scenarios where humans should be enabling it: people using older
> > stable releases who are crippled by some bug or other, and need to test
> > SRUs sooner rather than later.
>
> Well, this is a problem we solved a while ago - making use of
> Pin-Priority[0].
>
> With this enabled, a "sudo apt-get dist-upgrade" will not pull from
> -proposed, but
> sudo apt-get install xorg/saucy-proposed , would allow me to
> forcefully install xorg from saucy-proposed, as an opt-in - per
> package choice.
>
> [0] https://wiki.ubuntu.com/Testing/EnableProposed
What part of "not for humans" is confusing?
Scott K
--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
