Divesh Dutt
New Member
Hi guys i am trying to update ubuntu 17.04 to 18.04 but it is not updating and i am trying to install git and since 17.04 is no longer supported now i am not able to update that.Any solutions?
Problem with ubuntu 17.04
- Thread starter Divesh Dutt
- Start date
Hi @Divesh Dutt, and welcome! Not all Ubuntu versions would upgrade to 18.04 directly, and I think yours is one of them. You might could have upgraded to 17.10 and then to 18.04... but because your 17.04 has now reached "end-of-life"... that probably won't work with the Ubuntu Updater either. This is one of the reasons that it's usually better to run Long Term Support (LTS) versions.
But, I did find these instructions that may work for you. Be sure to backup important files before you begin! Good luck.
Cheers
But, I did find these instructions that may work for you. Be sure to backup important files before you begin! Good luck.
Cheers
OP
Divesh Dutt
New Member
I am trying to do that but whenever i try "sudo apt update"
It is throwing error
What would i do?
It is throwing error
What would i do?
arochester
Well-Known Member
EXACTLY what error?
OP
Divesh Dutt
New Member
Condobloke
Well-Known Member
Hi Divesh, well... I had only said that those instructions MAY work for you, and it seems that they did not. It may be possible to manually edit your sources.list file to still make the upgrade work, that would be time consuming and very prone to making mistakes in editing the file. Please remember that 17.04 is not supposed to update directly to 18.04 in the first place, so the instructions were a sort of trick to make it upgrade anyway.
Since it seems you are running Ubuntu in VirtualBox, I think @Condobloke's suggestion is excellent.... just install a fresh copy of 18.04 in a new virtual machine and go from there. Then you can take whatever time you need to bring data over from 17.04 to the new install.
For future reference, when you have multi-step instructions and the first step fails (like you show in your screen shots).... then it is better to just stop and not try to execute the following steps until you figure out the problem. You might make things worse!
Cheers
@Divesh Dutt - From the look of the error messages, it looks like a lot of the mirrors you have set up either do not exist, or do not have bionic repos in them.
Perhaps take a look at this list of official https mirrors for Ubuntu and try using one of them in sources.list instead:
https://www.reddit.com/r/Ubuntu/comments/3q53kc/list_of_ubuntu_repository_mirrors_available_over/
Note: if you don't have the apt-transport-https package installed, change the Https in the link to http instead.
Pick any one of those mirrors and then use it to update the base url of each of the main Ubuntu repos that you currently have set up in your sources.list. That should allow you to connect and update/upgrade.
E.g. If India is your closest server
Change:
To:
And do the same for the bionic-updates, bionic-security etc.
Once you have done that - try following the rest of the instructions to perform the update.
Perhaps take a look at this list of official https mirrors for Ubuntu and try using one of them in sources.list instead:
https://www.reddit.com/r/Ubuntu/comments/3q53kc/list_of_ubuntu_repository_mirrors_available_over/
Note: if you don't have the apt-transport-https package installed, change the Https in the link to http instead.
Pick any one of those mirrors and then use it to update the base url of each of the main Ubuntu repos that you currently have set up in your sources.list. That should allow you to connect and update/upgrade.
E.g. If India is your closest server
Change:
Code:
http://ca.old-releases.ubuntu.com/ubuntu bionic InReleaseTo:
Code:
http://ftp.iitm.ac.in/ubuntu bionic InReleaseAnd do the same for the bionic-updates, bionic-security etc.
Once you have done that - try following the rest of the instructions to perform the update.
OP
Divesh Dutt
New Member
Hi JasKinasis
so i am in sources.list but i can see two lines
deb http://ca.old-releases.ubuntu.com/ubuntu/ bionic main restricted
and
deb http://ca.old-releases.ubuntu.com/ubuntu/ bionic universe
which one do i need to edit.
sorry for lots of question i am new in linux.
so i am in sources.list but i can see two lines
deb http://ca.old-releases.ubuntu.com/ubuntu/ bionic main restricted
and
deb http://ca.old-releases.ubuntu.com/ubuntu/ bionic universe
which one do i need to edit.
sorry for lots of question i am new in linux.
Folks the OP (Original Poster, that's you, @Divesh Dutt ) is from Canada.
Divesh, short answer is both. But being where you are, the lines you would want to end up with would look like the following (choose one)
... of course with the bionic stuff following.
However, I am of the opinion that you do not need the "InRelease" in this instance. Jas might have other thoughts.
Also, with the article Stan (@atanere ) has referred to, where the "sed" command comes in, better to use, in your case, a variation which includes a [SUFFIX] option, as in
This will save your original sources.list as sources.bak so you have a backup to revert to if things go wrong.
Ultimately, though, and given you have already learned to use a Virtual Machine on which to install Zesty, is there a reason you do not wish to follow the advice of Brian (@Condobloke ) and Stan (@atanere ) above, and simply build another virtual install of Bionic Beaver? Is space a consideration? It would only require about 20GB.
Cheers
Chris Turner
wizardfromoz
BTW a belated welcome to linux.org
Divesh, short answer is both. But being where you are, the lines you would want to end up with would look like the following (choose one)
Code:
https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu/
#OR
https://mirror.its.sfu.ca/mirror/ubuntu/... of course with the bionic stuff following.
However, I am of the opinion that you do not need the "InRelease" in this instance. Jas might have other thoughts.
Also, with the article Stan (@atanere ) has referred to, where the "sed" command comes in, better to use, in your case, a variation which includes a [SUFFIX] option, as in
Code:
sudo sed -i.bak 's/zesty/bionic/g' /etc/apt/sources.listThis will save your original sources.list as sources.bak so you have a backup to revert to if things go wrong.
Ultimately, though, and given you have already learned to use a Virtual Machine on which to install Zesty, is there a reason you do not wish to follow the advice of Brian (@Condobloke ) and Stan (@atanere ) above, and simply build another virtual install of Bionic Beaver? Is space a consideration? It would only require about 20GB.
Cheers
Chris Turner
wizardfromoz
BTW a belated welcome to linux.org
If you're unsure - post your entire sources.list and we can advise on what changes to make.
Though, if this is a virtualbox image - then as the others have suggested you could just back up your personal data from that image and create a fresh VM with the latest version and then restore your personal data. That would save you from the headache of trying to manually upgrade such an old version.
TBH - I can't remember offhand what InRelease is used for. So it may or may not be needed. IDK! :/
I was just going with whatever the OP had in their existing config. I haven't used any Ubuntu or Ubuntu derived distros for a few years now (currently using Debian Testing, which is upstream from Ubuntu).
You're the Distro hopping Wiz - the wise one who runs all the Linuces - Or whatever the correct plural form of Linux is... Linux's? Linuxes? Linux's's'n's's? - either way - I'll defer to you on this one!
OP
Divesh Dutt
New Member
Alright guys i updated to 18.04 using fresh installation thanks for the help.
