Ubuntu upgrade from 17.04 to 18.04
14
I've installed ubuntu 17.04 and I want to upgrade it to 18.04. When I tried to do:
sudo do-release-upgrade
I got a message saying An upgrade from 'zesty' to 'bionic' is not supported with this tool. Need inputs to proceed on this.
sudo do-release-upgrade
Checking for a new Ubuntu release
Your Ubuntu release is not supported anymore.
For upgrade information, please visit:
http://www.ubuntu.com/releaseendoflife
Get:1 Upgrade tool signature [819 B]
Get:2 Upgrade tool [1,257 kB]
Fetched 1,258 kB in 0s (0 B/s)
authenticate 'bionic.tar.gz' against 'bionic.tar.gz.gpg'
extracting 'bionic.tar.gz'
Reading cache
Checking package manager
Can not upgrade
An upgrade from 'zesty' to 'bionic' is not supported with this tool.
ubuntu upgrade
edited Aug 3 '18 at 15:11
Jeff Schaller
39.3k1054125
asked Aug 3 '18 at 11:15
spaspa
88116
add a comment |
14
I've installed ubuntu 17.04 and I want to upgrade it to 18.04. When I tried to do:
sudo do-release-upgrade
I got a message saying An upgrade from 'zesty' to 'bionic' is not supported with this tool. Need inputs to proceed on this.
sudo do-release-upgrade
Checking for a new Ubuntu release
Your Ubuntu release is not supported anymore.
For upgrade information, please visit:
http://www.ubuntu.com/releaseendoflife
Get:1 Upgrade tool signature [819 B]
Get:2 Upgrade tool [1,257 kB]
Fetched 1,258 kB in 0s (0 B/s)
authenticate 'bionic.tar.gz' against 'bionic.tar.gz.gpg'
extracting 'bionic.tar.gz'
Reading cache
Checking package manager
Can not upgrade
An upgrade from 'zesty' to 'bionic' is not supported with this tool.
ubuntu upgrade
edited Aug 3 '18 at 15:11
Jeff Schaller
39.3k1054125
asked Aug 3 '18 at 11:15
spaspa
88116
Fill a bugreport.
– Ipor Sircer
Aug 3 '18 at 12:30
1
@IporSircer Please stop giving such an ill-advised recommendation. There are specific steps to fix the repositories and put the system up to date. Open source developers are not worthy of such lack of consideration of directing the hordes to them to give them end user support. I would not give end user support masked of bug reports if I were a developer, I have to work and pay my bills too. Have you ever filled an official bug report? I doubt normal end users will not be that happy doing that and doing it right.
– Rui F Ribeiro
Aug 3 '18 at 13:04
1
@RuiFRibeiro: This is the official way for upgrading: help.ubuntu.com/lts/serverguide/installing-upgrading.html . The developers wrote this. The poster followed the instruction and run into a problem. So this is a bug. Bug of documentation or bug ofdo-release-upgradecommand.
– Ipor Sircer
Aug 3 '18 at 13:21
2
"For upgrade information, please visit:http://www.ubuntu.com/releaseendoflife" Did you do that? What did you do with the information there?
– a CVn
Aug 3 '18 at 13:23
This really should be on AskUbuntu.
– tudor
Oct 3 '18 at 0:29
add a comment |
14
14
14
6
I've installed ubuntu 17.04 and I want to upgrade it to 18.04. When I tried to do:
sudo do-release-upgrade
I got a message saying An upgrade from 'zesty' to 'bionic' is not supported with this tool. Need inputs to proceed on this.
sudo do-release-upgrade
Checking for a new Ubuntu release
Your Ubuntu release is not supported anymore.
For upgrade information, please visit:
http://www.ubuntu.com/releaseendoflife
Get:1 Upgrade tool signature [819 B]
Get:2 Upgrade tool [1,257 kB]
Fetched 1,258 kB in 0s (0 B/s)
authenticate 'bionic.tar.gz' against 'bionic.tar.gz.gpg'
extracting 'bionic.tar.gz'
Reading cache
Checking package manager
Can not upgrade
An upgrade from 'zesty' to 'bionic' is not supported with this tool.
ubuntu upgrade
edited Aug 3 '18 at 15:11
Jeff Schaller
39.3k1054125
asked Aug 3 '18 at 11:15
spaspa
88116
I've installed ubuntu 17.04 and I want to upgrade it to 18.04. When I tried to do:
sudo do-release-upgrade
I got a message saying An upgrade from 'zesty' to 'bionic' is not supported with this tool. Need inputs to proceed on this.
sudo do-release-upgrade
Checking for a new Ubuntu release
Your Ubuntu release is not supported anymore.
For upgrade information, please visit:
http://www.ubuntu.com/releaseendoflife
Get:1 Upgrade tool signature [819 B]
Get:2 Upgrade tool [1,257 kB]
Fetched 1,258 kB in 0s (0 B/s)
authenticate 'bionic.tar.gz' against 'bionic.tar.gz.gpg'
extracting 'bionic.tar.gz'
Reading cache
Checking package manager
Can not upgrade
An upgrade from 'zesty' to 'bionic' is not supported with this tool.
ubuntu upgrade
ubuntu upgrade
edited Aug 3 '18 at 15:11
Jeff Schaller
39.3k1054125
asked Aug 3 '18 at 11:15
spaspa
88116
edited Aug 3 '18 at 15:11
Jeff Schaller
39.3k1054125
asked Aug 3 '18 at 11:15
spaspa
88116
edited Aug 3 '18 at 15:11
Jeff Schaller
39.3k1054125
edited Aug 3 '18 at 15:11
Jeff Schaller
39.3k1054125
edited Aug 3 '18 at 15:11
Jeff Schaller
39.3k1054125
39.3k1054125
asked Aug 3 '18 at 11:15
spaspa
88116
asked Aug 3 '18 at 11:15
spaspa
88116
asked Aug 3 '18 at 11:15
spaspa
88116
88116
Fill a bugreport.
– Ipor Sircer
Aug 3 '18 at 12:30
1
@IporSircer Please stop giving such an ill-advised recommendation. There are specific steps to fix the repositories and put the system up to date. Open source developers are not worthy of such lack of consideration of directing the hordes to them to give them end user support. I would not give end user support masked of bug reports if I were a developer, I have to work and pay my bills too. Have you ever filled an official bug report? I doubt normal end users will not be that happy doing that and doing it right.
– Rui F Ribeiro
Aug 3 '18 at 13:04
1
@RuiFRibeiro: This is the official way for upgrading: help.ubuntu.com/lts/serverguide/installing-upgrading.html . The developers wrote this. The poster followed the instruction and run into a problem. So this is a bug. Bug of documentation or bug ofdo-release-upgradecommand.
– Ipor Sircer
Aug 3 '18 at 13:21
2
"For upgrade information, please visit:http://www.ubuntu.com/releaseendoflife" Did you do that? What did you do with the information there?
– a CVn
Aug 3 '18 at 13:23
This really should be on AskUbuntu.
– tudor
Oct 3 '18 at 0:29
add a comment |
Fill a bugreport.
– Ipor Sircer
Aug 3 '18 at 12:30
1
@IporSircer Please stop giving such an ill-advised recommendation. There are specific steps to fix the repositories and put the system up to date. Open source developers are not worthy of such lack of consideration of directing the hordes to them to give them end user support. I would not give end user support masked of bug reports if I were a developer, I have to work and pay my bills too. Have you ever filled an official bug report? I doubt normal end users will not be that happy doing that and doing it right.
– Rui F Ribeiro
Aug 3 '18 at 13:04
1
@RuiFRibeiro: This is the official way for upgrading: help.ubuntu.com/lts/serverguide/installing-upgrading.html . The developers wrote this. The poster followed the instruction and run into a problem. So this is a bug. Bug of documentation or bug ofdo-release-upgradecommand.
– Ipor Sircer
Aug 3 '18 at 13:21
2
"For upgrade information, please visit:http://www.ubuntu.com/releaseendoflife" Did you do that? What did you do with the information there?
– a CVn
Aug 3 '18 at 13:23
This really should be on AskUbuntu.
– tudor
Oct 3 '18 at 0:29
Fill a bugreport.
– Ipor Sircer
Aug 3 '18 at 12:30
Fill a bugreport.
– Ipor Sircer
Aug 3 '18 at 12:30
1
1
@IporSircer Please stop giving such an ill-advised recommendation. There are specific steps to fix the repositories and put the system up to date. Open source developers are not worthy of such lack of consideration of directing the hordes to them to give them end user support. I would not give end user support masked of bug reports if I were a developer, I have to work and pay my bills too. Have you ever filled an official bug report? I doubt normal end users will not be that happy doing that and doing it right.
– Rui F Ribeiro
Aug 3 '18 at 13:04
@IporSircer Please stop giving such an ill-advised recommendation. There are specific steps to fix the repositories and put the system up to date. Open source developers are not worthy of such lack of consideration of directing the hordes to them to give them end user support. I would not give end user support masked of bug reports if I were a developer, I have to work and pay my bills too. Have you ever filled an official bug report? I doubt normal end users will not be that happy doing that and doing it right.
– Rui F Ribeiro
Aug 3 '18 at 13:04
1
1
@RuiFRibeiro: This is the official way for upgrading: help.ubuntu.com/lts/serverguide/installing-upgrading.html . The developers wrote this. The poster followed the instruction and run into a problem. So this is a bug. Bug of documentation or bug of
do-release-upgrade command.– Ipor Sircer
Aug 3 '18 at 13:21
@RuiFRibeiro: This is the official way for upgrading: help.ubuntu.com/lts/serverguide/installing-upgrading.html . The developers wrote this. The poster followed the instruction and run into a problem. So this is a bug. Bug of documentation or bug of
do-release-upgrade command.– Ipor Sircer
Aug 3 '18 at 13:21
2
2
"For upgrade information, please visit:
http://www.ubuntu.com/releaseendoflife" Did you do that? What did you do with the information there?– a CVn
Aug 3 '18 at 13:23
"For upgrade information, please visit:
http://www.ubuntu.com/releaseendoflife" Did you do that? What did you do with the information there?– a CVn
Aug 3 '18 at 13:23
This really should be on AskUbuntu.
– tudor
Oct 3 '18 at 0:29
This really should be on AskUbuntu.
– tudor
Oct 3 '18 at 0:29
add a comment |
1 Answer
1
active
oldest
votes
29
This was not properly explained anywhere, here is what you need to do (or how I did it):
Upgrade to 17.04 to 17.10:
Unable to upgrade from ubuntu 17.04 to 17.10
sudo cp /etc/apt/sources.list /etc/apt/sources.list.bak #to be safe
sudo sed -i -re 's/old-releases.ubuntu.com/archive.ubuntu.com/g' /etc/apt/sources.list
sudo sed -i -re 's/zesty/artful/g' /etc/apt/sources.list
sudo apt update
sudo apt dist-upgrade
sudo apt autoremove
(Links says to use aptitude instead of apt-get)
Upgrade from 17.10 to 18.04: EOLUpgrades
Replace everything in /etc/apt/sources.list with this:
## EOL upgrade sources.list
# Required
deb http://old-releases.ubuntu.com/ubuntu/ artful main restricted universe multiverse
deb http://old-releases.ubuntu.com/ubuntu/ artful-updates main restricted universe multiverse
deb http://old-releases.ubuntu.com/ubuntu/ artful-security main restricted universe multiverse
# Optional
#deb http://old-releases.ubuntu.com/ubuntu/ artful-backports main restricted universe multiverse
Then run the upgrade:
do-release-upgrade
Do what it says when asked and wait for it to finish and you should be done.
answered Aug 14 '18 at 9:08
uranibabauranibaba
41433
3
Excellent. Yes, I couldn't find a proper explanation either. The docs are really unclear. I think there is some confusion as to whether you're supposed to replace CODENAME in sources.list with your current release code name or the one you're trying to upgrade to. It's really not clear on that point.
– regularmike
Aug 29 '18 at 21:53
1
Thanks, this was really helpful. I had a "resolve generated breaks" error when I tried to usedo-release-upgrade. I solved it usingsudo apt-get update && sudo apt-get upgradefrom here, just in case it helps anyone else: askubuntu.com/questions/124845/…
– meenaparam
Sep 12 '18 at 15:04
I was very reluctant to run such manual upgrade, but I finally did it (the first part, from zesty to artful) and it went surprisingly well. Unless for one thing : the desktop session went away at some point, so I lost the terminal in which the upgrade was running, during the installation process. For some reason this interrupted, and could be resumed by running apt upgrade again. So I strongly suggest to run this inside screen, or tmux (byobu is great), or local text console (Ctrl Alt F3), or probably ssh session would be more stable than graphical local terminal.
– Franck
Nov 9 '18 at 9:58
I still got the same error when following this guide.
– jonneymendoza
Nov 26 '18 at 12:09
@jonneymendoza Are you on 17.04? Writelsb_release -ato get your version.
– uranibaba
Nov 27 '18 at 13:17
add a comment |
protected by Community♦ Jan 11 at 13:22
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
29
This was not properly explained anywhere, here is what you need to do (or how I did it):
Upgrade to 17.04 to 17.10:
Unable to upgrade from ubuntu 17.04 to 17.10
sudo cp /etc/apt/sources.list /etc/apt/sources.list.bak #to be safe
sudo sed -i -re 's/old-releases.ubuntu.com/archive.ubuntu.com/g' /etc/apt/sources.list
sudo sed -i -re 's/zesty/artful/g' /etc/apt/sources.list
sudo apt update
sudo apt dist-upgrade
sudo apt autoremove
(Links says to use aptitude instead of apt-get)
Upgrade from 17.10 to 18.04: EOLUpgrades
Replace everything in /etc/apt/sources.list with this:
## EOL upgrade sources.list
# Required
deb http://old-releases.ubuntu.com/ubuntu/ artful main restricted universe multiverse
deb http://old-releases.ubuntu.com/ubuntu/ artful-updates main restricted universe multiverse
deb http://old-releases.ubuntu.com/ubuntu/ artful-security main restricted universe multiverse
# Optional
#deb http://old-releases.ubuntu.com/ubuntu/ artful-backports main restricted universe multiverse
Then run the upgrade:
do-release-upgrade
Do what it says when asked and wait for it to finish and you should be done.
answered Aug 14 '18 at 9:08
uranibabauranibaba
41433
3
Excellent. Yes, I couldn't find a proper explanation either. The docs are really unclear. I think there is some confusion as to whether you're supposed to replace CODENAME in sources.list with your current release code name or the one you're trying to upgrade to. It's really not clear on that point.
– regularmike
Aug 29 '18 at 21:53
1
Thanks, this was really helpful. I had a "resolve generated breaks" error when I tried to usedo-release-upgrade. I solved it usingsudo apt-get update && sudo apt-get upgradefrom here, just in case it helps anyone else: askubuntu.com/questions/124845/…
– meenaparam
Sep 12 '18 at 15:04
I was very reluctant to run such manual upgrade, but I finally did it (the first part, from zesty to artful) and it went surprisingly well. Unless for one thing : the desktop session went away at some point, so I lost the terminal in which the upgrade was running, during the installation process. For some reason this interrupted, and could be resumed by running apt upgrade again. So I strongly suggest to run this inside screen, or tmux (byobu is great), or local text console (Ctrl Alt F3), or probably ssh session would be more stable than graphical local terminal.
– Franck
Nov 9 '18 at 9:58
I still got the same error when following this guide.
– jonneymendoza
Nov 26 '18 at 12:09
@jonneymendoza Are you on 17.04? Writelsb_release -ato get your version.
– uranibaba
Nov 27 '18 at 13:17
add a comment |
29
This was not properly explained anywhere, here is what you need to do (or how I did it):
Upgrade to 17.04 to 17.10:
Unable to upgrade from ubuntu 17.04 to 17.10
sudo cp /etc/apt/sources.list /etc/apt/sources.list.bak #to be safe
sudo sed -i -re 's/old-releases.ubuntu.com/archive.ubuntu.com/g' /etc/apt/sources.list
sudo sed -i -re 's/zesty/artful/g' /etc/apt/sources.list
sudo apt update
sudo apt dist-upgrade
sudo apt autoremove
(Links says to use aptitude instead of apt-get)
Upgrade from 17.10 to 18.04: EOLUpgrades
Replace everything in /etc/apt/sources.list with this:
## EOL upgrade sources.list
# Required
deb http://old-releases.ubuntu.com/ubuntu/ artful main restricted universe multiverse
deb http://old-releases.ubuntu.com/ubuntu/ artful-updates main restricted universe multiverse
deb http://old-releases.ubuntu.com/ubuntu/ artful-security main restricted universe multiverse
# Optional
#deb http://old-releases.ubuntu.com/ubuntu/ artful-backports main restricted universe multiverse
Then run the upgrade:
do-release-upgrade
Do what it says when asked and wait for it to finish and you should be done.
answered Aug 14 '18 at 9:08
uranibabauranibaba
41433
3
Excellent. Yes, I couldn't find a proper explanation either. The docs are really unclear. I think there is some confusion as to whether you're supposed to replace CODENAME in sources.list with your current release code name or the one you're trying to upgrade to. It's really not clear on that point.
– regularmike
Aug 29 '18 at 21:53
1
Thanks, this was really helpful. I had a "resolve generated breaks" error when I tried to usedo-release-upgrade. I solved it usingsudo apt-get update && sudo apt-get upgradefrom here, just in case it helps anyone else: askubuntu.com/questions/124845/…
– meenaparam
Sep 12 '18 at 15:04
I was very reluctant to run such manual upgrade, but I finally did it (the first part, from zesty to artful) and it went surprisingly well. Unless for one thing : the desktop session went away at some point, so I lost the terminal in which the upgrade was running, during the installation process. For some reason this interrupted, and could be resumed by running apt upgrade again. So I strongly suggest to run this inside screen, or tmux (byobu is great), or local text console (Ctrl Alt F3), or probably ssh session would be more stable than graphical local terminal.
– Franck
Nov 9 '18 at 9:58
I still got the same error when following this guide.
– jonneymendoza
Nov 26 '18 at 12:09
@jonneymendoza Are you on 17.04? Writelsb_release -ato get your version.
– uranibaba
Nov 27 '18 at 13:17
add a comment |
29
29
29
This was not properly explained anywhere, here is what you need to do (or how I did it):
Upgrade to 17.04 to 17.10:
Unable to upgrade from ubuntu 17.04 to 17.10
sudo cp /etc/apt/sources.list /etc/apt/sources.list.bak #to be safe
sudo sed -i -re 's/old-releases.ubuntu.com/archive.ubuntu.com/g' /etc/apt/sources.list
sudo sed -i -re 's/zesty/artful/g' /etc/apt/sources.list
sudo apt update
sudo apt dist-upgrade
sudo apt autoremove
(Links says to use aptitude instead of apt-get)
Upgrade from 17.10 to 18.04: EOLUpgrades
Replace everything in /etc/apt/sources.list with this:
## EOL upgrade sources.list
# Required
deb http://old-releases.ubuntu.com/ubuntu/ artful main restricted universe multiverse
deb http://old-releases.ubuntu.com/ubuntu/ artful-updates main restricted universe multiverse
deb http://old-releases.ubuntu.com/ubuntu/ artful-security main restricted universe multiverse
# Optional
#deb http://old-releases.ubuntu.com/ubuntu/ artful-backports main restricted universe multiverse
Then run the upgrade:
do-release-upgrade
Do what it says when asked and wait for it to finish and you should be done.
answered Aug 14 '18 at 9:08
uranibabauranibaba
41433
This was not properly explained anywhere, here is what you need to do (or how I did it):
Upgrade to 17.04 to 17.10:
Unable to upgrade from ubuntu 17.04 to 17.10
sudo cp /etc/apt/sources.list /etc/apt/sources.list.bak #to be safe
sudo sed -i -re 's/old-releases.ubuntu.com/archive.ubuntu.com/g' /etc/apt/sources.list
sudo sed -i -re 's/zesty/artful/g' /etc/apt/sources.list
sudo apt update
sudo apt dist-upgrade
sudo apt autoremove
(Links says to use aptitude instead of apt-get)
Upgrade from 17.10 to 18.04: EOLUpgrades
Replace everything in /etc/apt/sources.list with this:
## EOL upgrade sources.list
# Required
deb http://old-releases.ubuntu.com/ubuntu/ artful main restricted universe multiverse
deb http://old-releases.ubuntu.com/ubuntu/ artful-updates main restricted universe multiverse
deb http://old-releases.ubuntu.com/ubuntu/ artful-security main restricted universe multiverse
# Optional
#deb http://old-releases.ubuntu.com/ubuntu/ artful-backports main restricted universe multiverse
Then run the upgrade:
do-release-upgrade
Do what it says when asked and wait for it to finish and you should be done.
answered Aug 14 '18 at 9:08
uranibabauranibaba
41433
answered Aug 14 '18 at 9:08
uranibabauranibaba
41433
answered Aug 14 '18 at 9:08
uranibabauranibaba
41433
answered Aug 14 '18 at 9:08
uranibabauranibaba
41433
41433
3
Excellent. Yes, I couldn't find a proper explanation either. The docs are really unclear. I think there is some confusion as to whether you're supposed to replace CODENAME in sources.list with your current release code name or the one you're trying to upgrade to. It's really not clear on that point.
– regularmike
Aug 29 '18 at 21:53
1
Thanks, this was really helpful. I had a "resolve generated breaks" error when I tried to usedo-release-upgrade. I solved it usingsudo apt-get update && sudo apt-get upgradefrom here, just in case it helps anyone else: askubuntu.com/questions/124845/…
– meenaparam
Sep 12 '18 at 15:04
I was very reluctant to run such manual upgrade, but I finally did it (the first part, from zesty to artful) and it went surprisingly well. Unless for one thing : the desktop session went away at some point, so I lost the terminal in which the upgrade was running, during the installation process. For some reason this interrupted, and could be resumed by running apt upgrade again. So I strongly suggest to run this inside screen, or tmux (byobu is great), or local text console (Ctrl Alt F3), or probably ssh session would be more stable than graphical local terminal.
– Franck
Nov 9 '18 at 9:58
I still got the same error when following this guide.
– jonneymendoza
Nov 26 '18 at 12:09
@jonneymendoza Are you on 17.04? Writelsb_release -ato get your version.
– uranibaba
Nov 27 '18 at 13:17
add a comment |
3
Excellent. Yes, I couldn't find a proper explanation either. The docs are really unclear. I think there is some confusion as to whether you're supposed to replace CODENAME in sources.list with your current release code name or the one you're trying to upgrade to. It's really not clear on that point.
– regularmike
Aug 29 '18 at 21:53
1
Thanks, this was really helpful. I had a "resolve generated breaks" error when I tried to usedo-release-upgrade. I solved it usingsudo apt-get update && sudo apt-get upgradefrom here, just in case it helps anyone else: askubuntu.com/questions/124845/…
– meenaparam
Sep 12 '18 at 15:04
I was very reluctant to run such manual upgrade, but I finally did it (the first part, from zesty to artful) and it went surprisingly well. Unless for one thing : the desktop session went away at some point, so I lost the terminal in which the upgrade was running, during the installation process. For some reason this interrupted, and could be resumed by running apt upgrade again. So I strongly suggest to run this inside screen, or tmux (byobu is great), or local text console (Ctrl Alt F3), or probably ssh session would be more stable than graphical local terminal.
– Franck
Nov 9 '18 at 9:58
I still got the same error when following this guide.
– jonneymendoza
Nov 26 '18 at 12:09
@jonneymendoza Are you on 17.04? Writelsb_release -ato get your version.
– uranibaba
Nov 27 '18 at 13:17
3
3
Excellent. Yes, I couldn't find a proper explanation either. The docs are really unclear. I think there is some confusion as to whether you're supposed to replace CODENAME in sources.list with your current release code name or the one you're trying to upgrade to. It's really not clear on that point.
– regularmike
Aug 29 '18 at 21:53
Excellent. Yes, I couldn't find a proper explanation either. The docs are really unclear. I think there is some confusion as to whether you're supposed to replace CODENAME in sources.list with your current release code name or the one you're trying to upgrade to. It's really not clear on that point.
– regularmike
Aug 29 '18 at 21:53
1
1
Thanks, this was really helpful. I had a "resolve generated breaks" error when I tried to use
do-release-upgrade. I solved it using sudo apt-get update && sudo apt-get upgrade from here, just in case it helps anyone else: askubuntu.com/questions/124845/…– meenaparam
Sep 12 '18 at 15:04
Thanks, this was really helpful. I had a "resolve generated breaks" error when I tried to use
do-release-upgrade. I solved it using sudo apt-get update && sudo apt-get upgrade from here, just in case it helps anyone else: askubuntu.com/questions/124845/…– meenaparam
Sep 12 '18 at 15:04
I was very reluctant to run such manual upgrade, but I finally did it (the first part, from zesty to artful) and it went surprisingly well. Unless for one thing : the desktop session went away at some point, so I lost the terminal in which the upgrade was running, during the installation process. For some reason this interrupted, and could be resumed by running apt upgrade again. So I strongly suggest to run this inside screen, or tmux (byobu is great), or local text console (Ctrl Alt F3), or probably ssh session would be more stable than graphical local terminal.
– Franck
Nov 9 '18 at 9:58
I was very reluctant to run such manual upgrade, but I finally did it (the first part, from zesty to artful) and it went surprisingly well. Unless for one thing : the desktop session went away at some point, so I lost the terminal in which the upgrade was running, during the installation process. For some reason this interrupted, and could be resumed by running apt upgrade again. So I strongly suggest to run this inside screen, or tmux (byobu is great), or local text console (Ctrl Alt F3), or probably ssh session would be more stable than graphical local terminal.
– Franck
Nov 9 '18 at 9:58
I still got the same error when following this guide.
– jonneymendoza
Nov 26 '18 at 12:09
I still got the same error when following this guide.
– jonneymendoza
Nov 26 '18 at 12:09
@jonneymendoza Are you on 17.04? Write
lsb_release -a to get your version.– uranibaba
Nov 27 '18 at 13:17
@jonneymendoza Are you on 17.04? Write
lsb_release -a to get your version.– uranibaba
Nov 27 '18 at 13:17
add a comment |
protected by Community♦ Jan 11 at 13:22
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
Fill a bugreport.
– Ipor Sircer
Aug 3 '18 at 12:30
1
@IporSircer Please stop giving such an ill-advised recommendation. There are specific steps to fix the repositories and put the system up to date. Open source developers are not worthy of such lack of consideration of directing the hordes to them to give them end user support. I would not give end user support masked of bug reports if I were a developer, I have to work and pay my bills too. Have you ever filled an official bug report? I doubt normal end users will not be that happy doing that and doing it right.
– Rui F Ribeiro
Aug 3 '18 at 13:04
1
@RuiFRibeiro: This is the official way for upgrading: help.ubuntu.com/lts/serverguide/installing-upgrading.html . The developers wrote this. The poster followed the instruction and run into a problem. So this is a bug. Bug of documentation or bug of
do-release-upgradecommand.– Ipor Sircer
Aug 3 '18 at 13:21
2
"For upgrade information, please visit:
http://www.ubuntu.com/releaseendoflife" Did you do that? What did you do with the information there?– a CVn
Aug 3 '18 at 13:23
This really should be on AskUbuntu.
– tudor
Oct 3 '18 at 0:29