[Bug 1199157] Update Released

Steve Langasek steve.langasek at canonical.com
Wed Jul 17 18:35:19 UTC 2013


The verification of this Stable Release Update has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regresssions.

-- 
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