View Full Version : [SOLVED] Which of all these ways to upgrade LTS from 16.04.3 to 18.04?

April 25th, 2018, 06:21 AM
Long ago I installed 16.04.3 LTS from a server variant iso, then added kubuntu. After so much customizing, I'd prefer not to have to do a fresh install once 18.04 is released.

Some quick Googling leads me to more upgrade options than I was aware of previously. I have all these PPAs, & I'm not sure which method handles that best.


/etc/apt/sources.list.d/brandonsnider-ubuntu-cdrtools-xenial.list:deb http://ppa.launchpad.net/brandonsnider/cdrtools/ubuntu xenial main
/etc/apt/sources.list.d/git-core-ubuntu-ppa-xenial.list:deb http://ppa.launchpad.net/git-core/ppa/ubuntu xenial main
/etc/apt/sources.list.d/google-chrome.list:deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
/etc/apt/sources.list.d/libreoffice-ubuntu-ppa-xenial.list:deb http://ppa.launchpad.net/libreoffice/ppa/ubuntu xenial main
/etc/apt/sources.list.d/skype-stable.list:deb [arch=amd64] https://repo.skype.com/deb stable main
/etc/apt/sources.list.d/slack.list:deb https://packagecloud.io/slacktechnologies/slack/debian/ jessie main
/etc/apt/sources.list.d/spideroakone.list:deb http://APT.spideroak.com/ubuntu-spideroak-hardy/ release restricted
/etc/apt/sources.list.d/ubuntu-wine-ubuntu-ppa-xenial.list:deb http://ppa.launchpad.net/ubuntu-wine/ppa/ubuntu xenial main
/etc/apt/sources.list.d/ubuntu-x-swat-ubuntu-updates-xenial.list:deb http://ppa.launchpad.net/ubuntu-x-swat/updates/ubuntu xenial main
/etc/apt/sources.list.d/virtualbox-ppa.list:deb http://download.virtualbox.org/virtualbox/debian xenial contrib
/etc/apt/sources.list.d/webupd8team-ubuntu-java-xenial.list:deb http://ppa.launchpad.net/webupd8team/java/ubuntu xenial main
/etc/apt/sources.list.d/yannubuntu-ubuntu-boot-repair-xenial.list:deb http://ppa.launchpad.net/yannubuntu/boot-repair/ubuntu xenial main

So this is what I'm basing the timing of all this on:

For the server variant I found this, which looks easy enough, but has caveats* apparently:
*LTS systems are only automatically considered for an upgrade to the next LTS via do-release-upgrade with the first point release.

This is a recent, albeit non-official tutorial detailing a few methods:

Again, not sure which way would handle my PPA's, or if I should just do it manually- as is mentioned in the 'Debian Way' part of the aforementioned article.

April 25th, 2018, 07:02 AM
update-manager and do-release-upgrade method disables ppa's and 3rd party repos.
The debian way updates all sources to the new release codename including ppa's and 3rd party repos.

For Ubuntu it is better to run it the update-manager/do-release-upgrade way.

Per ppa, you'll need to read the fine print usually of the ppa or 3rd party repository about how to go about dealing with them.
Some, like google-chrome,. can be disabled and then simply re-enabled.
And then some will require you purge them out with ppa-purge.

Case in point, you'll need to ppa-purge the x-swat ppa:

If you are upgrading from one release to another with this PPA activated, please install the ppa-purge package and use it to downgrade everything in here beforehand. sudo ppa-purge ppa:ubuntu-x-swat/updates will do it.

So you'll have to search for which can be disabled and which need more done.

April 25th, 2018, 11:33 AM
Just do a fresh install.

April 25th, 2018, 11:37 AM
+1 with monkeybrain. I have never had any luck upgrading from one version to the next.

I once tried it on 13 machines: one worked, one was somewhat easy to fix, the other 11 all had to be redone.