wily release upgrader needs to support upgrades from Trusty

Bug #1537916 reported by Brian Murray
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-release-upgrader (Ubuntu)
Won't Fix
High
Unassigned
Wily
Fix Released
High
Brian Murray

Bug Description

Test Case
---------
1) Modify /etc/update-manager/meta-release URI line to be http://www.murraytwins.com/tmp/meta-release (This is only necessary because Vivid is still a supported release.)
2) Ensure /etc/update-manager/release-upgrades has Prompt=normal
3) Run do-release-upgrade

Observe an error dialog indicating that release upgrades aren't supported with this tool. Using 'do-release-upgrade -p' you should receive no such error message.

DistUpgrade.cfg and demoted.cfg need creating / modifying to support dist upgrades from Trusty to Wily.

Changed in ubuntu-release-upgrader (Ubuntu):
status: New → In Progress
assignee: nobody → Brian Murray (brian-murray)
importance: Undecided → High
Changed in ubuntu-release-upgrader (Ubuntu Wily):
status: New → In Progress
importance: Undecided → High
assignee: nobody → Brian Murray (brian-murray)
Changed in ubuntu-release-upgrader (Ubuntu):
status: In Progress → Won't Fix
assignee: Brian Murray (brian-murray) → nobody
description: updated
Revision history for this message
Chris J Arges (arges) wrote : Please test proposed package

Hello Brian, or anyone else affected,

Accepted ubuntu-release-upgrader into wily-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-release-upgrader/1:15.10.14.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 Wily):
status: In Progress → Fix Committed
tags: added: verification-needed
tags: added: wily
Revision history for this message
Brian Murray (brian-murray) wrote :

Tested this and /tmp/ubuntu-release-upgrader-$TEMP/ has DistUpgrade.cfg.trusty which contains the following:

[Sources]
From=trusty
To=wily
ValidOrigin=Ubuntu
ValidMirrors = mirrors.cfg
Components=main,restricted,universe,multiverse
Pockets=security,updates,proposed,backports
;AllowThirdParty=False

So its verified.

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

---------------
ubuntu-release-upgrader (1:15.10.14.3) wily-proposed; urgency=medium

  * Add in data files (DistUpgrade.cfg.trusty, demoted.cfg.trusty) to support
    distribution upgrades from Trusty to Wily. (LP: #1537916)

 -- Brian Murray <email address hidden> Mon, 25 Jan 2016 13:48:41 -0800

Changed in ubuntu-release-upgrader (Ubuntu Wily):
status: Fix Committed → Fix Released
Revision history for this message
Brian Murray (brian-murray) wrote : Update Released

The verification of the Stable Release Update for ubuntu-release-upgrader 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 regressions.

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

Other bug subscribers

Remote bug watches

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