Problems Upgrading from 17.04 (EOL Jan2018)
Clash Royale CLAN TAG#URR8PPP up vote
0
down vote
favorite
All,
I have read a number of threads regarding this, in May 2018.
I am no expert user of Terminal, but have tried all the suggestions in
How to install software or upgrade from an old unsupported release?.
I have also tried the GUI approach, also included in 91815, which appeared to work with all but the last step.
The return was 'error during update', 'aborting', 'restoring original system state'
This laptop is not regularly used (hence missing the update date), but has returned to a stable, usable state.
Any suggestions please on what I need to do differently to get away from 17.04/Zesty and onto an LTS??
Please note I am far from expert.
Thanks.
upgrade 17.04 unsupported-packages
asked May 21 at 10:20
Jonathan Airey
1
add a comment |Â
up vote
0
down vote
favorite
All,
I have read a number of threads regarding this, in May 2018.
I am no expert user of Terminal, but have tried all the suggestions in
How to install software or upgrade from an old unsupported release?.
I have also tried the GUI approach, also included in 91815, which appeared to work with all but the last step.
The return was 'error during update', 'aborting', 'restoring original system state'
This laptop is not regularly used (hence missing the update date), but has returned to a stable, usable state.
Any suggestions please on what I need to do differently to get away from 17.04/Zesty and onto an LTS??
Please note I am far from expert.
Thanks.
upgrade 17.04 unsupported-packages
asked May 21 at 10:20
Jonathan Airey
1
I'm a little confused sorry. You stated you "returned [your laptop] to a stable & usable state" & "tried all suggestions" in the post; as I read it the end result is if you follow steps, you'll end up on a supported release (note: it has multiple answers, & I didn't read all) Are you still running 17.04? or 17.10? or 18.04 LTS already? Thedo-release-upgradestep in the post jumps your eol-release to a later one! (if on 17.10 -do-release-upgradewill bump you to 18.04)
– guiverc
May 21 at 10:45
I apologise if my post post appears ambiguous. It was, and is on 17.04. I didnt return it to the 'original system state', that was the message after it tried, but had not applied the upgrade. It did download many files, but appeared not to have applied any of them. Would it help if I attached the log??
– Jonathan Airey
May 21 at 16:46
Backup. then to upgrade a release yourself; the/etc/apt/sources.listneed only point to the next release (ie. 'zesty' (17.04) references get changed to 'artful') then you re-load repo.lists (orsudo apt-get update) then dist-upgrade (sudo apt-get dist-upgrade) Ideally you should update 17.04 first (which requiresarchive.ubuntu.combe changed toold-releases.ubuntu.comwith any country code removed - which the linked post's scripts miss) but after that update it needs restoration (thedo-release-upgrademay do this). Reboot is necessary to use 17.10.
– guiverc
May 22 at 0:03
Since you want to go to a LTS, you then change 'artful' to 'bionic' in the sources file,apt update ; apt dist-upgrade; reboot and you're on 18.04. You could just do this last step, though (ie. go straight from 17.04 to 18.04) but it's more likely to have issues due to significance of change (skipped release, let alone the unity->gnome significant change). It's up to you. If you added non-standard ppa/repos to your system they should be disabled before any of this, and I realize you like gui(mouse) but I can't help there (gui tools expect pre-EOL, plus I'm unfamiliar)
– guiverc
May 22 at 0:08
Thanks Guiverc. I tried this, but it still didnt work. But then I added '-backports' to the source list, and it worked cleanly. I went from zesty to artful by this method. Then a regular upgrade to 18.04. All sorted. All good. Thanks. MODS: this can be marked as FIXED and Closed.
– Jonathan Airey
May 22 at 6:12
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
All,
I have read a number of threads regarding this, in May 2018.
I am no expert user of Terminal, but have tried all the suggestions in
How to install software or upgrade from an old unsupported release?.
I have also tried the GUI approach, also included in 91815, which appeared to work with all but the last step.
The return was 'error during update', 'aborting', 'restoring original system state'
This laptop is not regularly used (hence missing the update date), but has returned to a stable, usable state.
Any suggestions please on what I need to do differently to get away from 17.04/Zesty and onto an LTS??
Please note I am far from expert.
Thanks.
upgrade 17.04 unsupported-packages
asked May 21 at 10:20
Jonathan Airey
1
All,
I have read a number of threads regarding this, in May 2018.
I am no expert user of Terminal, but have tried all the suggestions in
How to install software or upgrade from an old unsupported release?.
I have also tried the GUI approach, also included in 91815, which appeared to work with all but the last step.
The return was 'error during update', 'aborting', 'restoring original system state'
This laptop is not regularly used (hence missing the update date), but has returned to a stable, usable state.
Any suggestions please on what I need to do differently to get away from 17.04/Zesty and onto an LTS??
Please note I am far from expert.
Thanks.
upgrade 17.04 unsupported-packages
asked May 21 at 10:20
Jonathan Airey
1
asked May 21 at 10:20
Jonathan Airey
1
asked May 21 at 10:20
Jonathan Airey
1
asked May 21 at 10:20
Jonathan Airey
1
1
I'm a little confused sorry. You stated you "returned [your laptop] to a stable & usable state" & "tried all suggestions" in the post; as I read it the end result is if you follow steps, you'll end up on a supported release (note: it has multiple answers, & I didn't read all) Are you still running 17.04? or 17.10? or 18.04 LTS already? Thedo-release-upgradestep in the post jumps your eol-release to a later one! (if on 17.10 -do-release-upgradewill bump you to 18.04)
– guiverc
May 21 at 10:45
I apologise if my post post appears ambiguous. It was, and is on 17.04. I didnt return it to the 'original system state', that was the message after it tried, but had not applied the upgrade. It did download many files, but appeared not to have applied any of them. Would it help if I attached the log??
– Jonathan Airey
May 21 at 16:46
Backup. then to upgrade a release yourself; the/etc/apt/sources.listneed only point to the next release (ie. 'zesty' (17.04) references get changed to 'artful') then you re-load repo.lists (orsudo apt-get update) then dist-upgrade (sudo apt-get dist-upgrade) Ideally you should update 17.04 first (which requiresarchive.ubuntu.combe changed toold-releases.ubuntu.comwith any country code removed - which the linked post's scripts miss) but after that update it needs restoration (thedo-release-upgrademay do this). Reboot is necessary to use 17.10.
– guiverc
May 22 at 0:03
Since you want to go to a LTS, you then change 'artful' to 'bionic' in the sources file,apt update ; apt dist-upgrade; reboot and you're on 18.04. You could just do this last step, though (ie. go straight from 17.04 to 18.04) but it's more likely to have issues due to significance of change (skipped release, let alone the unity->gnome significant change). It's up to you. If you added non-standard ppa/repos to your system they should be disabled before any of this, and I realize you like gui(mouse) but I can't help there (gui tools expect pre-EOL, plus I'm unfamiliar)
– guiverc
May 22 at 0:08
Thanks Guiverc. I tried this, but it still didnt work. But then I added '-backports' to the source list, and it worked cleanly. I went from zesty to artful by this method. Then a regular upgrade to 18.04. All sorted. All good. Thanks. MODS: this can be marked as FIXED and Closed.
– Jonathan Airey
May 22 at 6:12
add a comment |Â
I'm a little confused sorry. You stated you "returned [your laptop] to a stable & usable state" & "tried all suggestions" in the post; as I read it the end result is if you follow steps, you'll end up on a supported release (note: it has multiple answers, & I didn't read all) Are you still running 17.04? or 17.10? or 18.04 LTS already? Thedo-release-upgradestep in the post jumps your eol-release to a later one! (if on 17.10 -do-release-upgradewill bump you to 18.04)
– guiverc
May 21 at 10:45
I apologise if my post post appears ambiguous. It was, and is on 17.04. I didnt return it to the 'original system state', that was the message after it tried, but had not applied the upgrade. It did download many files, but appeared not to have applied any of them. Would it help if I attached the log??
– Jonathan Airey
May 21 at 16:46
Backup. then to upgrade a release yourself; the/etc/apt/sources.listneed only point to the next release (ie. 'zesty' (17.04) references get changed to 'artful') then you re-load repo.lists (orsudo apt-get update) then dist-upgrade (sudo apt-get dist-upgrade) Ideally you should update 17.04 first (which requiresarchive.ubuntu.combe changed toold-releases.ubuntu.comwith any country code removed - which the linked post's scripts miss) but after that update it needs restoration (thedo-release-upgrademay do this). Reboot is necessary to use 17.10.
– guiverc
May 22 at 0:03
Since you want to go to a LTS, you then change 'artful' to 'bionic' in the sources file,apt update ; apt dist-upgrade; reboot and you're on 18.04. You could just do this last step, though (ie. go straight from 17.04 to 18.04) but it's more likely to have issues due to significance of change (skipped release, let alone the unity->gnome significant change). It's up to you. If you added non-standard ppa/repos to your system they should be disabled before any of this, and I realize you like gui(mouse) but I can't help there (gui tools expect pre-EOL, plus I'm unfamiliar)
– guiverc
May 22 at 0:08
Thanks Guiverc. I tried this, but it still didnt work. But then I added '-backports' to the source list, and it worked cleanly. I went from zesty to artful by this method. Then a regular upgrade to 18.04. All sorted. All good. Thanks. MODS: this can be marked as FIXED and Closed.
– Jonathan Airey
May 22 at 6:12
I'm a little confused sorry. You stated you "returned [your laptop] to a stable & usable state" & "tried all suggestions" in the post; as I read it the end result is if you follow steps, you'll end up on a supported release (note: it has multiple answers, & I didn't read all) Are you still running 17.04? or 17.10? or 18.04 LTS already? The
do-release-upgrade step in the post jumps your eol-release to a later one! (if on 17.10 - do-release-upgrade will bump you to 18.04)– guiverc
May 21 at 10:45
I'm a little confused sorry. You stated you "returned [your laptop] to a stable & usable state" & "tried all suggestions" in the post; as I read it the end result is if you follow steps, you'll end up on a supported release (note: it has multiple answers, & I didn't read all) Are you still running 17.04? or 17.10? or 18.04 LTS already? The
do-release-upgrade step in the post jumps your eol-release to a later one! (if on 17.10 - do-release-upgrade will bump you to 18.04)– guiverc
May 21 at 10:45
I apologise if my post post appears ambiguous. It was, and is on 17.04. I didnt return it to the 'original system state', that was the message after it tried, but had not applied the upgrade. It did download many files, but appeared not to have applied any of them. Would it help if I attached the log??
– Jonathan Airey
May 21 at 16:46
I apologise if my post post appears ambiguous. It was, and is on 17.04. I didnt return it to the 'original system state', that was the message after it tried, but had not applied the upgrade. It did download many files, but appeared not to have applied any of them. Would it help if I attached the log??
– Jonathan Airey
May 21 at 16:46
Backup. then to upgrade a release yourself; the
/etc/apt/sources.list need only point to the next release (ie. 'zesty' (17.04) references get changed to 'artful') then you re-load repo.lists (or sudo apt-get update) then dist-upgrade (sudo apt-get dist-upgrade) Ideally you should update 17.04 first (which requires archive.ubuntu.com be changed to old-releases.ubuntu.com with any country code removed - which the linked post's scripts miss) but after that update it needs restoration (the do-release-upgrade may do this). Reboot is necessary to use 17.10.– guiverc
May 22 at 0:03
Backup. then to upgrade a release yourself; the
/etc/apt/sources.list need only point to the next release (ie. 'zesty' (17.04) references get changed to 'artful') then you re-load repo.lists (or sudo apt-get update) then dist-upgrade (sudo apt-get dist-upgrade) Ideally you should update 17.04 first (which requires archive.ubuntu.com be changed to old-releases.ubuntu.com with any country code removed - which the linked post's scripts miss) but after that update it needs restoration (the do-release-upgrade may do this). Reboot is necessary to use 17.10.– guiverc
May 22 at 0:03
Since you want to go to a LTS, you then change 'artful' to 'bionic' in the sources file,
apt update ; apt dist-upgrade ; reboot and you're on 18.04. You could just do this last step, though (ie. go straight from 17.04 to 18.04) but it's more likely to have issues due to significance of change (skipped release, let alone the unity->gnome significant change). It's up to you. If you added non-standard ppa/repos to your system they should be disabled before any of this, and I realize you like gui(mouse) but I can't help there (gui tools expect pre-EOL, plus I'm unfamiliar)– guiverc
May 22 at 0:08
Since you want to go to a LTS, you then change 'artful' to 'bionic' in the sources file,
apt update ; apt dist-upgrade ; reboot and you're on 18.04. You could just do this last step, though (ie. go straight from 17.04 to 18.04) but it's more likely to have issues due to significance of change (skipped release, let alone the unity->gnome significant change). It's up to you. If you added non-standard ppa/repos to your system they should be disabled before any of this, and I realize you like gui(mouse) but I can't help there (gui tools expect pre-EOL, plus I'm unfamiliar)– guiverc
May 22 at 0:08
Thanks Guiverc. I tried this, but it still didnt work. But then I added '-backports' to the source list, and it worked cleanly. I went from zesty to artful by this method. Then a regular upgrade to 18.04. All sorted. All good. Thanks. MODS: this can be marked as FIXED and Closed.
– Jonathan Airey
May 22 at 6:12
Thanks Guiverc. I tried this, but it still didnt work. But then I added '-backports' to the source list, and it worked cleanly. I went from zesty to artful by this method. Then a regular upgrade to 18.04. All sorted. All good. Thanks. MODS: this can be marked as FIXED and Closed.
– Jonathan Airey
May 22 at 6:12
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Â
draft saved
draft discarded
Â
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1038644%2fproblems-upgrading-from-17-04-eol-jan2018%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
I'm a little confused sorry. You stated you "returned [your laptop] to a stable & usable state" & "tried all suggestions" in the post; as I read it the end result is if you follow steps, you'll end up on a supported release (note: it has multiple answers, & I didn't read all) Are you still running 17.04? or 17.10? or 18.04 LTS already? The
do-release-upgradestep in the post jumps your eol-release to a later one! (if on 17.10 -do-release-upgradewill bump you to 18.04)– guiverc
May 21 at 10:45
I apologise if my post post appears ambiguous. It was, and is on 17.04. I didnt return it to the 'original system state', that was the message after it tried, but had not applied the upgrade. It did download many files, but appeared not to have applied any of them. Would it help if I attached the log??
– Jonathan Airey
May 21 at 16:46
Backup. then to upgrade a release yourself; the
/etc/apt/sources.listneed only point to the next release (ie. 'zesty' (17.04) references get changed to 'artful') then you re-load repo.lists (orsudo apt-get update) then dist-upgrade (sudo apt-get dist-upgrade) Ideally you should update 17.04 first (which requiresarchive.ubuntu.combe changed toold-releases.ubuntu.comwith any country code removed - which the linked post's scripts miss) but after that update it needs restoration (thedo-release-upgrademay do this). Reboot is necessary to use 17.10.– guiverc
May 22 at 0:03
Since you want to go to a LTS, you then change 'artful' to 'bionic' in the sources file,
apt update ; apt dist-upgrade; reboot and you're on 18.04. You could just do this last step, though (ie. go straight from 17.04 to 18.04) but it's more likely to have issues due to significance of change (skipped release, let alone the unity->gnome significant change). It's up to you. If you added non-standard ppa/repos to your system they should be disabled before any of this, and I realize you like gui(mouse) but I can't help there (gui tools expect pre-EOL, plus I'm unfamiliar)– guiverc
May 22 at 0:08
Thanks Guiverc. I tried this, but it still didnt work. But then I added '-backports' to the source list, and it worked cleanly. I went from zesty to artful by this method. Then a regular upgrade to 18.04. All sorted. All good. Thanks. MODS: this can be marked as FIXED and Closed.
– Jonathan Airey
May 22 at 6:12