[Bug 1199157] Re: proposed should be disabled on upgrade to development release
Launchpad Bug Tracker
1199157 at bugs.launchpad.net
Wed Jul 17 18:35:20 UTC 2013
This bug was fixed in the package ubuntu-release-upgrader - 1:0.192.12
---------------
ubuntu-release-upgrader (1:0.192.12) raring-proposed; urgency=low
* pass along devel-release switch to the dist-upgrader so that proposed
repositories can be disabled if one is upgrading to the the development
release (LP: #1199157)
-- Brian Murray <brian at ubuntu.com> Thu, 11 Jul 2013 10:33:45 -0700
** Changed in: ubuntu-release-upgrader (Ubuntu Raring)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubuntu-release-upgrader in
Ubuntu.
https://bugs.launchpad.net/bugs/1199157
Title:
proposed should be disabled on upgrade to development release
Status in “ubuntu-release-upgrader” package in Ubuntu:
Fix Released
Status in “ubuntu-release-upgrader” source package in Raring:
Fix Released
Bug description:
[Impact]
People upgrading from Raring, with -proposed enabled, to Saucy will still have -proposed enabled. Because -proposed is used as a tested bed in Ubuntu+1 this can result in a terrible experience for people.
[Test Case]
0) Add raring-proposed to /etc/apt/sources.list
1) Run do-release-upgrade -d
2) Upgrade to saucy
3) Observe that /etc/apt/sources.list has saucy-proposed enabled
(Its also possible to inspect /etc/apt/sources.list after it has been
rewritten, when you are presented with the final upgrade prompt, and
observe that saucy-proposed is present in it.)
With the version of ubuntu-release-upgrader from raring-proposed
you'll notice that /etc/apt/sources.list has a comment indicating that
saucy-proposed is not for humans.
[Regression Potential]
Very little as we are just passing the --devel-release option along to the dist upgrader.
Original Description
--------------------
proposed is now used as a testbed and staging area in Ubuntu+1 and is not to be used by humans. I just installed raring in a VM, enabled proposed, and the upgraded with 'do-release-upgrade -d' When finished, proposed is enabled and packages from proposed are installed. There's no guarantee that proposed will even be installable.
It should be disabled on upgrade to development release.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1199157/+subscriptions
More information about the foundations-bugs
mailing list