upgrading from an End of Life release is not easy peasy

Bug #1745754 reported by Scott Carle
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ubuntu-release-upgrader (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

There is no good path for non technical users to upgrade end of life versions of Ubuntu.

Explanation and suggestion below.

I am a 25 year user of linux and at least a decade on ubuntu. I also am an it professional so have little problem diving below the interface to fix stuff or do non standard configuration. However I prefer stuff to just work and not have to go below the hood so to say. More importantly is all those people that simply don't have the ability to go below the hood. I was running Zesty which was released just over a year ago and suddenly was unable to update or do a dist upgrade. I understand it was not a LTS release and am ok with updates not happening, but I was running it because 17.10 broke some of my software I use. However there is no upgrade path on a zesty computer at this time without manually changing your apt sources files. To me this is unacceptable.

My suggestion is to even if you disable updates or even installation of other software from the repositories for the outdated distro that you leave the ability to do a dist upgrade. It could be as simple as a option to dist upgrade that runs a scrip like I just ran to change to the archived version of the zesty repository and then rant the dist upgrade. I can also think of several other ways.

what I did was use
sudo sed -i -re 's/([a-z]{2}\.)?archive.ubuntu.com|security.ubuntu.com/old-releases.ubuntu.com/g' /etc/apt/sources.list
and then
sudo apt-get update && sudo apt-get dist-upgrade

For a technical user this is a relatively easy fix to the problem. For a non technical user that is a multi year educational journey to learn how to do this, they don't want this knowledge they just want their computer to work. I know that it should be a fairly easy fix for the people that maintain the gui upgrade.

My wife or mom or many other people I have using Ubuntu desktops wouldn't know how to do this. It is a major failure point as a desktop to have a version just over a year old that someone can't click a button to update to the next version. I would propose that it shouldn't matter how old it is that there should always be left a standard upgrade path to the next version even if you are no longer supporting it. This type of major disconnect in usability is what pushes normal computer users to just go back to windows or mac. Even I was really irritated that I had to figure out why updating and installing software quit working and then figure out how to fix it.

My overall suggestion would be not to archive older distro's just put in a pop up when you update or install software that your distro is no longer supported and click here to update. It would seem to be a fairly simple solution.

Revision history for this message
Colin Watson (cjwatson) wrote :

We do need to move the files off archive.ubuntu.com for space reasons on mirrors, but (1) that's not actually done by Launchpad as such, but by Ubuntu's end-of-life processes, and (b) this is the kind of thing that ought to be handled by the distribution's upgrade tools. I've heard a few developers talking recently about the need to improve this. Reassigning over to ubuntu-release-upgrader.

affects: launchpad → ubuntu-release-upgrader (Ubuntu)
Revision history for this message
Scott Carle (audeojude) wrote :

Sorry, didn't realize it put it in the wrong place. Thank you for moving it to where it needs to be.

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

This may be a duplicate of bug 1744722 but its hard to tell without any log files.

summary: - Dist Upgrade Path Bug
+ upgrading from an End of Life release is not easy peasy
Revision history for this message
Scott Carle (audeojude) wrote :

I don't believe it has anything to do with non standard 3rd party apt sources. I had disabled all of them other than the bone stock ubuntu sources. Also I had no issue upgrading at all after i fixed the location of the servers to the archives. This is simply a complaint that there is no upgrade path other than manually changing repositories to the archives on a now unsupported release. It is bad human ergonomics :)

I did note that there was a bug in the updater with bug https://bugs.launchpad.net/bugs/1744722 I did not have any issues with upgrading once the source list servers info was corrected.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubuntu-release-upgrader (Ubuntu):
status: New → Confirmed
Revision history for this message
Mikolaj Buchwald (mikbuch) wrote :

@Scott Carle, I had a very similar problem.

I got "An upgrade from ‘groovy’ to ‘impish’ is not supported with this tool." error when I was trying to upgrade my EOL end-of-life Ubuntu release with use `do-release-upgrade` (command line). I have some initial notes no that: https://gist.github.com/mikbuch/2c349e1281c69818b48893a460c5accb

As my problem is slightly different, namely, I'd like the `do-release-upgrade` support EOL upgrades as well, I will create a new issue for that. Nevertheless, I very much agree with you, that what would be very helpful for Ubuntu users (especially the less technical ones), is better support for (EOL) release upgrades. I have upvoted your bug (the current issue) and subscribed the notifications.

Revision history for this message
Scott Carle (audeojude) wrote :

It seems to be a very simple issue. do upgrade already tells you what version you have and if there is an upgrade path on new releases. Why can't it do that for every release going back into antiquity. There are probably only 40ish official releases that would need to be covered. When a release is archived you only need to update the sources for that release to point the updater to the archives as opposed to the latest supported releases. I'm a advanced user not a programmer but if I can address it on the command line with this line of code to make it work on a case by case basis

sudo sed -i -re 's/([a-z]{2}\.)?archive.ubuntu.com|security.ubuntu.com/old-releases.ubuntu.com/g' /etc/apt/sources.list
and then
sudo apt-get update && sudo apt-get dist-upgrade

how hard would it be to create this in the normal upgrade process for each of the old releases.

Revision history for this message
Scott Carle (audeojude) wrote :

Wouldn't it just be an extensive list of if/then conditional statements that covered all the official and point releases? Once done the first time it would only be updated each time a new release was released or an old one was archived to make sure it pointed to the correct path for the upgrade for whatever version you were running.

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

@Mikolaj Buchwald - I opened a separate bug report regarding your specific issue in bug 1975533.

Revision history for this message
Mikolaj Buchwald (mikbuch) wrote :

@Scott Carle, I agree.

@Brian Murray,thank you!

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.