Ubuntu
ubuntu-release-upgrader package

need to support upgrades from 12.10 to 13.10

Bug #1258639 reported by Brian Murray
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-release-upgrader (Ubuntu)
Invalid
High
Unassigned
Quantal
Invalid
Undecided
Unassigned
Saucy
Fix Released
High
Brian Murray
update-manager (Ubuntu)
Invalid
High
Unassigned
Quantal
Fix Released
High
Brian Murray
Saucy
Invalid
Undecided
Unassigned

Bug Description

N.B. update-manager should not be release to quantal-updates until after Raring has become End of Life as people may still want to upgrade to Raring from Quantal.

[Test Case]
There is not an easy way to test that this doesn't work as the meta-release file on changelogs.ubuntu.com indicates and will continue to indicate that Raring is supported. However, one can test upgrades from Quantal to Saucy via the following:

1) Install the version of update-manager form quantal-proposed
2) Run update-manager -c -p
3) Observe a dialog box that indicating that Ubuntu 13.10 is available and that you have Ubuntu 12.10.
4) Choose to Upgrade
5) Observe release announcement for Ubuntu 13.10
6) Continue to upgrade to Ubuntu 13.10

Due to the way releases of Ubuntu will be reaching End of Life (Ubuntu 13.04 becomes EOL before Ubuntu 12.10) we need to create an upgrade path for users of 12.10. It has been decided that we will have them upgrade from 12.10 to 13.10, because 14.04 doesn't come out until April 2014 the same time that Ubuntu 13.04 become EOL.

For this upgrade to be possible two changes will need to occur. In the 12.10 version of update-manager the code will need to be changed so that an upgrade from Quantal to Saucy is possible. This will be staged in -proposed for testing and when Raring becomes EOL it will be released to -updates.

In addition to the above change, the saucy version of the release upgrader will be need to be modified to allow upgrades from Quantal to Saucy. This can be done by creating a new DistUpgrade.cfg file named DistUpgrade.cfg.quantal which will have changes relevant to the upgrade from Quantal to Saucy.

See original description
Brian Murray (brian-murray)
Changed in ubuntu-release-upgrader (Ubuntu):
status: New → Triaged
importance: Undecided → High
assignee: nobody → Brian Murray (brian-murray)
Changed in update-manager (Ubuntu):
status: New → Triaged
importance: Undecided → High
assignee: nobody → Brian Murray (brian-murray)
Brian Murray (brian-murray)
Changed in update-manager (Ubuntu Quantal):
status: New → In Progress
importance: Undecided → High
assignee: nobody → Brian Murray (brian-murray)
Changed in update-manager (Ubuntu):
status: Triaged → Invalid
Changed in ubuntu-release-upgrader (Ubuntu Quantal):
status: New → Invalid
Changed in update-manager (Ubuntu):
assignee: Brian Murray (brian-murray) → nobody
Changed in update-manager (Ubuntu Saucy):
status: New → Invalid
Changed in ubuntu-release-upgrader (Ubuntu Saucy):
status: New → In Progress
importance: Undecided → High
assignee: nobody → Brian Murray (brian-murray)
Changed in ubuntu-release-upgrader (Ubuntu):
status: Triaged → Invalid
assignee: Brian Murray (brian-murray) → nobody
Revision history for this message
Stéphane Graber (stgraber) wrote : Please test proposed package

Hello Brian, or anyone else affected,

Accepted ubuntu-release-upgrader into saucy-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/ubuntu-release-upgrader/1:0.205.3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in ubuntu-release-upgrader (Ubuntu Saucy):
status: In Progress → Fix Committed
tags: added: verification-needed
Brian Murray (brian-murray)
description: updated
Revision history for this message
Steve Langasek (vorlon) wrote :

Hello Brian, or anyone else affected,

Accepted update-manager into quantal-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/update-manager/1:0.174.5 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in update-manager (Ubuntu Quantal):
status: In Progress → Fix Committed
Revision history for this message
Brian Murray (brian-murray) wrote :

The upload of ubuntu-release-upgrader to saucy-proposed did not have all the necessary changes as the release upgrader tarball did not actually include DistUpgrade.cfg.quantal and demoted.cfg.quantal was a broken symlink. I've resolved this with a new upload in the saucy -proposed queue.

description: updated
Revision history for this message
Brian Murray (brian-murray) wrote :

Using the dist-upgrader tarball produced on 2013-12-16 I was able to perform a distribution upgrade from Quantal to Saucy using the version of update-manager from -proposed and update-manager -c -p. I did experience a compiz crash during the process so ended up upgrading using the text version of the upgrader (do-release-upgrade -f DistUpgradeViewText -p), regardless the upgrade process worked.

I'm marking this a verification done, however while it is fine to SRU release ubuntu-release-upgrader in Saucy the release of update-manager should wait until Raring becomes End of Life.

tags: added: verification-done
removed: verification-needed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ubuntu-release-upgrader - 1:0.205.4

---------------
ubuntu-release-upgrader (1:0.205.4) saucy-proposed; urgency=low

  * Ensure quantal specific files (DistUpgrade.cfg and demoted.cfg) are in the
    release upgrader tarball
 -- Brian Murray <email address hidden> Thu, 12 Dec 2013 17:10:36 -0800

Changed in ubuntu-release-upgrader (Ubuntu Saucy):
status: Fix Committed → Fix Released
Brian Murray (brian-murray)
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package update-manager - 1:0.174.5

---------------
update-manager (1:0.174.5) quantal-proposed; urgency=low

  * UpdateManager/Core/MetaRelease.py: support upgrades from Quantal to Saucy
    because Raring is becoming End of Life before Quantal (LP: #1258639)
 -- Brian Murray <email address hidden> Fri, 06 Dec 2013 12:39:35 -0800

Changed in update-manager (Ubuntu Quantal):
status: Fix Committed → Fix Released
Revision history for this message
Steve Langasek (vorlon) wrote : Update Released

The verification of the Stable Release Update for update-manager 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.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.