How to install software or upgrade from an old unsupported release?Upgrading from the command line?Can I keep using Ubuntu 9.04 if it's outdated?How to upgrade from Ubuntu 10.10 to 11.04?Updating ubuntu server apt-get gives me - 404 Not FoundInstalling ubuntu 16.04 without losing dataWhat to do when can't update anymore with apt-get?Ubuntu 13.04 all apt-get mirrors downFailed to fetch repositoriesNot able to install software on Ubuntu 12.10In Ubuntu 13.04, cannot install libssl-devUnable to find new release ( after interuppting a release upgrade)How do I upgrade from an LTS release to the next point release?Release configuration problem with Synaptic Package ManagerHow to trace the origin of how updates make it into my Ubuntu machine?Can't upgrade from 15.10 to 16.04Install an old OpenShot release in Ubuntu 18.04
Lock screen if I leave my seat?
Is it possible to conserve the total kinetic energy of a system, but not its momentum?
Why didn't classical music use drums?
Creating 123456 in the fewest number of steps
How can communicating in human language with an unconscious alien species be treated as an attack?
Fill your bucket with 2020
How to appropriately quit a "bad" unpaid internship?
Should I sign a NDA that holds me liable for legal fees even if I am in the right?
lightning:card Icon size
Sort-of Alexa clone using Python on a raspberry pi
What sort of professional boundary should I set with other students when I am a grader for a class I will be taking?
What to do if some panel members walk out while I'm being interviewed?
(x | y) - y why can't it simply be x or even `x | 0`
What does “critical but stable” mean?
Fill the Golfeek gutter
Visting the UK with my own car
How and why is my site being abused?
How are the Van der Waals constants a and b related to each other?
What happens when a photon "dies"?
Why can't I shoot with a fast shutter speed?
Can the U.S. Senate hold an impeachment trial if the House "passes" but does not "deliver" articles of impeachment?
When does one use an extra stave for piano music?
Reuse a part of a tikz picture with savebox
Creating 2020 in the fewest number of steps
How to install software or upgrade from an old unsupported release?
Upgrading from the command line?Can I keep using Ubuntu 9.04 if it's outdated?How to upgrade from Ubuntu 10.10 to 11.04?Updating ubuntu server apt-get gives me - 404 Not FoundInstalling ubuntu 16.04 without losing dataWhat to do when can't update anymore with apt-get?Ubuntu 13.04 all apt-get mirrors downFailed to fetch repositoriesNot able to install software on Ubuntu 12.10In Ubuntu 13.04, cannot install libssl-devUnable to find new release ( after interuppting a release upgrade)How do I upgrade from an LTS release to the next point release?Release configuration problem with Synaptic Package ManagerHow to trace the origin of how updates make it into my Ubuntu machine?Can't upgrade from 15.10 to 16.04Install an old OpenShot release in Ubuntu 18.04
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;
Recently I have installed an older version of Ubuntu on my old machine. Whenever I try to install any software, I get an error saying it couldn't be found:
$ sudo apt-get install vlc
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Couldn't find package vlc
release-management
add a comment
|
Recently I have installed an older version of Ubuntu on my old machine. Whenever I try to install any software, I get an error saying it couldn't be found:
$ sudo apt-get install vlc
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Couldn't find package vlc
release-management
2
It might be worth editing some (or all) answers to this question, as during the weekend after spending quite a while trying to make this work I have by luck realized that they have moved over fromhttp://old-releases.ubuntu.com/ubuntu/
tohttp://us.archive.ubuntu.com/ubuntu/
(or your own respective two letter abbreviated county code at the beginning) starting from 17.10 (essentially in sync with going back to the beginning of the alphabet).
– Isti115
May 6 at 22:22
add a comment
|
Recently I have installed an older version of Ubuntu on my old machine. Whenever I try to install any software, I get an error saying it couldn't be found:
$ sudo apt-get install vlc
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Couldn't find package vlc
release-management
Recently I have installed an older version of Ubuntu on my old machine. Whenever I try to install any software, I get an error saying it couldn't be found:
$ sudo apt-get install vlc
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Couldn't find package vlc
release-management
release-management
edited Feb 27 '17 at 4:34
Zanna
55.8k15 gold badges152 silver badges258 bronze badges
55.8k15 gold badges152 silver badges258 bronze badges
asked Dec 31 '11 at 18:29
made_in_indiamade_in_india
4,0733 gold badges14 silver badges14 bronze badges
4,0733 gold badges14 silver badges14 bronze badges
2
It might be worth editing some (or all) answers to this question, as during the weekend after spending quite a while trying to make this work I have by luck realized that they have moved over fromhttp://old-releases.ubuntu.com/ubuntu/
tohttp://us.archive.ubuntu.com/ubuntu/
(or your own respective two letter abbreviated county code at the beginning) starting from 17.10 (essentially in sync with going back to the beginning of the alphabet).
– Isti115
May 6 at 22:22
add a comment
|
2
It might be worth editing some (or all) answers to this question, as during the weekend after spending quite a while trying to make this work I have by luck realized that they have moved over fromhttp://old-releases.ubuntu.com/ubuntu/
tohttp://us.archive.ubuntu.com/ubuntu/
(or your own respective two letter abbreviated county code at the beginning) starting from 17.10 (essentially in sync with going back to the beginning of the alphabet).
– Isti115
May 6 at 22:22
2
2
It might be worth editing some (or all) answers to this question, as during the weekend after spending quite a while trying to make this work I have by luck realized that they have moved over from
http://old-releases.ubuntu.com/ubuntu/
to http://us.archive.ubuntu.com/ubuntu/
(or your own respective two letter abbreviated county code at the beginning) starting from 17.10 (essentially in sync with going back to the beginning of the alphabet).– Isti115
May 6 at 22:22
It might be worth editing some (or all) answers to this question, as during the weekend after spending quite a while trying to make this work I have by luck realized that they have moved over from
http://old-releases.ubuntu.com/ubuntu/
to http://us.archive.ubuntu.com/ubuntu/
(or your own respective two letter abbreviated county code at the beginning) starting from 17.10 (essentially in sync with going back to the beginning of the alphabet).– Isti115
May 6 at 22:22
add a comment
|
9 Answers
9
active
oldest
votes
The repositories for older releases that are not supported (like 11.04, 11.10 and 13.04) get moved to an archive server. There are repositories available at http://old-releases.ubuntu.com.
The reason for this is that it is now out of support and no longer receiving updates and security patches.
I would urge you to consider a supported distribution. If your computer is too old in terms of memory or processor then you should consider a distribution such as Lubuntu or Xubuntu.
If you want to continue using an outdated release then edit /etc/apt/sources.list
and change archive.ubuntu.com
and security.ubuntu.com
to old-releases.ubuntu.com
.
You can do this with sed
:
sudo sed -i -re 's/([a-z]2.)?archive.ubuntu.com|security.ubuntu.com/old-releases.ubuntu.com/g' /etc/apt/sources.list
then update with:
sudo apt-get update && sudo apt-get dist-upgrade
Sometimes, it might be faster to create backups of your system and reinstall using supported release instead.
Source: Can I keep using Ubuntu 9.04 if it's outdated?
To upgrade to a new release:
Once you have performed the above steps to switch to the old-releases mirrors, update the Update Manager and then do do-release-upgrade
:
sudo apt-get update
sudo apt-get install update-manager-core
sudo do-release-upgrade
See also EOLUpgrades - Community Help Wiki.
9
and, just for the sake of completeness... what aboutextras
repository (for Skype etc)? Are they available anywhere after EOF?
– MestreLion
Apr 27 '13 at 1:00
2
an easier way issudo vi /etc/apt/sources.list
and modify it manually. I had to do it because I'm quite new and I don't know sed to make this work for karmic, Thanks, Your answer is still valid and correct.
– bhathiya-perera
Dec 3 '13 at 19:08
19
An even easier way issudo nano /etc/apt/sources.list
, asvi*
is just annoying...
– Wilf
Mar 1 '14 at 18:35
4
Thesed
command doesn't always work, as there are mirrors that are run by organizations outside ofubuntu.com
. I'm not even sure that there are three dots for all of the domain names. For those, you must manually edit/etc/apt/sources.list
.
– Olathe
Jul 9 '15 at 5:06
3
There is an issue with this in upgrading from 15.04 as of 3/21/17. Vivid is no longer supported, however the dist is not on old-releases.
– Matthew Titsworth
Mar 21 '17 at 20:07
|
show 4 more comments
What are 404 errors
The 404 or Not Found error message is a HTTP standard response code
indicating that the client was able to communicate with the server,
but the server could not find what was requested.
The web site hosting server will typically generate "404 - Page Not
Found" web page, when users attempts to follow a broken or dead link.
Why are we facing 404 errors
Ubuntu follows the approach of two different release cycles:
Normal Ubuntu releases are supported for 9 months. LTS releases are supported for 5 years.
Past releases may have different support schedules (for example, normal releases (before 13.04) used to be supported for 18 months, while LTS releases (before 12.04) used to be supported for 3 years on the desktop and 5 years on the server).
EOL: Once the support period for a particular release is over; they are called End Of Life (EOL) and all the updates and package repositories for that Release are transferred to a different server which results in 404 errors while running sudo apt-get update
. You can confirm if your release has become EOL by going to this page. If your Ubuntu release is mentioned under "End Of Life (EOL)" Table, then the release is no longer supported and you should try to upgrade to a newer supported release. However, if you wish to continue using this unsupported release, you would have to make necessary modifications in /etc/apt/sources.list
to point to the old-releases
server of Ubuntu.
Steps to make necessary modifications
Open your Terminal:
- Press Ctrl + Alt + T; OR
- If you have Gnome:
Applications
→Accessories
→Terminal
; OR - If you have Unity: press Super (the key between Left Ctrl and Left Alt) and query for
Terminal
.
Run the following command to enter into root shell:
sudo -i
input your user password and press Enter. The prompt would change and would indicate that the root user is now logged in. Here run the following command:
gedit /etc/apt/sources.list
The file would open in a new Gedit window. Find the first line which doesn't start with
#
. Suppose you are running Karmic Koala (Ubuntu 9.10): it should be like the following line:deb <siteurl> karmic main restricted
where,
<siteurl>
is your preferred server -http://gb.archive.ubuntu.com/ubuntu
in your case (for example).Press Ctrl + H to replace your
<siteurl>
withhttp://old-releases.ubuntu.com/ubuntu
.- Search for:
http://gb.archive.ubuntu.com/ubuntu
ie;<siteurl>
- Replace with:
http://old-releases.ubuntu.com/ubuntu
and - Press Replace All
- Search for:
Once again:
- Search for:
http://security.ubuntu.com/ubuntu
(this exact url for all the Ubuntu Releases — whatever be the present server that you are using) - Replace with:
http://old-releases.ubuntu.com/ubuntu
- Press Replace All
- Search for:
Save your file and exit Gedit.
Run the following command to get out of root shell:
logout
You would find that the prompt switches back to indicate that your normal user is now logged in. Then run the following:
sudo apt-get update
There you go. No 404 Errors this time. You can now install all the available packages for your Ubuntu Release. You can also run sudo apt-get dist-upgrade
to install any Security/Bug-fix updates which have not yet been installed but you won't get any further Security/Bug-fix updates from Ubuntu.
6
+1 for also including instructions to update the security repo.
– Gaffi
Mar 16 '13 at 16:07
Actually the first line without a # wasraring main restricted
, no deb whatsoever. I changed it as specified, and then also replaced the urls, but still got 404s.
– Yokhen
Oct 23 '14 at 23:11
2
@Yokhen If the line didn't begin withdeb <siteurl>
, then most likely your/etc/apt/sources.list
file has become corrupted due to some reason. Please follow the answers given at: How do I restore the default repositories?. That would restore the correct/etc/apt/sources.list
for you and then follow my answer to change the servers to point to the old-releases server.
– Aditya
Oct 24 '14 at 8:15
thanks! Somehow I managed to upgrade from 13.04 to 13.10 though, and now I'm on my way to 14.04.
– Yokhen
Oct 24 '14 at 8:56
1
@Dan, modified the answer, now we enter into root shell and then run the graphical program. No need to use gksudo anymore. I want to keep this answer for the novice users like me and don't want to complicate matters with using terminal based editors, however easy or powerful they may be.
– Aditya
Jul 17 '16 at 13:56
|
show 4 more comments
The short answer is to add the next apt repository to the Third-Party Software (or Other Software in newer versions) in Software Sources (or Software & Updates in newer versions):
deb http://old-releases.ubuntu.com/ubuntu code_name main restricted universe multiverse
The long answer...
GUI Method
Well, actually we will do this without to use any terminal. Not even once. Just GUI, I promise ;-)
First, open Software Sources (or Software & Updates in newer versions). It does not matter how old is your Ubuntu, there is certainly something like this. For Ubuntu 9.04 (Jaunty Jackalope) look at next image to see where is located:
After Software Sources (or Software & Updates) it is open, go in Ubuntu Software and Updates tabs and unselect everytiyng like in next pictures. You don't need this things anymore since your Ubuntu version is End of Life:
Without closing Software Sources (or Software & Updates), go in Third-Party Software (for newest releases this tab is named Other Software) tab and add a new apt repository. Insert exactly next line when you are asked:
deb http://old-releases.ubuntu.com/ubuntu jaunty main restricted universe multiverse
If your version of Ubuntu is other than 9.04, replace in the above line jaunty
with your Ubuntu codename (for example if you have Ubuntu 9.10, replace with karmic
and so on):
Now, when you will close Software Sources (or Software & Updates) you will be asked to reload the information about available software. Just be sure that you have a working internet connection:
And now you are free to download almost whatever you want. For 9.04 you can use Synaptic Package Manager. For newest releases there is Ubuntu Software Center.
For example to install VLC in Ubuntu 9.04 using Synaptic Package Manager, follow the instructions in the following pictures:
If you want to Update your Ubuntu to a new release, just go to System > Update Manager:
I tested this method from a live session of Ubuntu 9.04 (Jaunty Jackalope) and as you can see from these pictures it worked. If you are on an installed session of Ubuntu you will be asked sometimes for root or admin password. Just insert your personal user password when you are asked.
1
I just did all this from installed 10.10 (maverick) version. Everything well good as described. @Radu, your answer is flawless!
– Gediminas Jeremiah Gudelis
Aug 28 '13 at 20:01
1
Those images needs updating... wait... what are you doing with a pre-12.04?
– Braiam
Dec 30 '13 at 14:01
1
@Braiam Those images are up to date. If you will give a try to Ubuntu 9.04 (Jaunty Jackalope), you will understand.
– Radu Rădeanu
Mar 22 '14 at 19:49
1
@RaduRădeanu Ubuntu 9.04 was my first foray into the linux world. Ahh, those screenshots bring back memories!
– Tyzoid
Apr 13 '14 at 22:03
Cannot get this to work for 15.04 to be upgraded to 16.04. Can't get past adding the new APT line please help.
– MrMule
Oct 10 '16 at 18:34
|
show 1 more comment
I got here since I could not upgrade a system from 15.10 (EOL) to 16.04. But none of the answers worked for me... even after doing everything that was suggested here I kept getting from sudo do-release-upgrade
the annoying response:
Checking for a new Ubuntu release
No new release found
And I had no success in running update-manager
; it kept throwing exceptions which I could not resolve. I suspect something is corrupted in my 15.10 installation, but the bottom line is that the built-in upgrades just fail.
So I looked for a non-built-in method, and sure enough I found it looking at this answer.
Here is the solution that worked for me:
- Open http://changelogs.ubuntu.com/meta-release
- Locate the release you want to upgrade to. In my case it is Xenial Xerus (16.04 Long Term Support).
- Locate the UpgradeTool URL. For xenial it is this one. Download the tarball from that URL into an empty folder and and open it (
tar -xzf
or using the GUI). Locate the executable file with the same name as the distribution (in my case
xenial
). Run it withsudo
:sudo ./xenial &
Approve the upgrade, and wait for the download to complete - there's thousands of files and likely over a Gigabyte. Proceed with installing the upgrade...
(Edited long after I performed the upgrade... It was successful and I forgot to update)
Wait until it completes, approve if asked... I don't recall the exact details
After the reboot the new version is running successfully, and all updates can be fetched normally.
1
It took me a while to find this post. Only using the referenced tarball I succeeded in getting the upgrade running from 15.04 / wily. The approaches using the old-releases urls did not work. I hope this helps other users getting into this problem.
– Jeroen
Dec 19 '16 at 9:34
I'm glad you found it helpful!
– laugh
Dec 21 '16 at 19:35
1
Seriously thanks for this, I just used these steps to upgrade 10.04 to 12.04. My issue was different in that my install wasn't corrupted, but there was an error on do-release-upgrade which I was unable to find in the terminal. Following these steps popped up a dialog telling me "error authenticating some packages" which led me to askubuntu.com/a/426121/262601 which DID allow the upgrade to continue successfully. Was pulling my hair out, but its my own fault for not upgrading sooner.
– Fooxz
Jan 6 '17 at 0:27
Unfortunately, not even this works for 15.04
– MiroJanosik
Jan 22 '18 at 18:32
Works as a charm! I had a zesty server that i neglected and I got it to artful and could upgrade further from there, thanks!
– Patrick Cornelissen
Aug 6 '18 at 7:18
|
show 1 more comment
To get apt-get
working again, change your software sources to the old release repositories.
gksudo gedit /etc/apt/sources.list
delete whatever is in there, and paste the following:
# Required
deb http://old-releases.ubuntu.com/ubuntu/ karmic main restricted universe multiverse
deb http://old-releases.ubuntu.com/ubuntu/ karmic-updates main restricted universe multiverse
deb http://old-releases.ubuntu.com/ubuntu/ karmic-security main restricted universe multiverse
# Optional
#deb http://old-releases.ubuntu.com/ubuntu/ karmic-backports main restricted universe multiverse
That's all.
Thanks mikewhatever, but the result is the same when I try "apt-get install lm-sensors". Maybe there's another missing source: "Reading package lists... Done Building dependency tree Reading state information... Done Package lm-sensors is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package lm-sensors has no installation candidate"
– Rorro
Apr 13 '12 at 10:55
Here are the debs: old-releases.ubuntu.com/ubuntu/pool/main/l/lm-sensors-3. I trust it, you've reloaded the sources list, right?
– mikewhatever
Apr 13 '12 at 12:08
This answer does not work... Why does it have so many upvotes? Did anybody actually test it?
– Tomáš Zato - Reinstate Monica
Aug 15 '14 at 11:00
I've tested it, but the real question is: Why are you still on Karmic? It's been out of support for years, and you should really move on to a more recent release.
– mikewhatever
Aug 15 '14 at 12:13
add a comment
|
While fossfreedom's answer does a good job of describing and solving the problem, I've found a variant solution that I think is easier and a little more elegant.
The trick is to add http://old-releases.ubuntu.com/ubuntu/
as a mirror, and then tell Software Sources to switch to that mirror.
To do this, backup and edit /usr/share/python-apt/templates/Ubuntu.mirrors
. Choose a fake location for the old-releases server (e.g. #LOC:US
), and add the following line under it:
#LOC:US
http://old-releases.ubuntu.com/ubuntu/
Now open the system's Software Sources dialog, and manually select old-releases.ubuntu.com
as though it were your regional mirror. You should find it listed under the fake location you chose in the previous step.
The next time you reload your package information via Synaptic or Update Manager, you should see it successfully retrieving updated package information.
Works fine, very easy & quick
– doug
Jul 22 '14 at 1:42
add a comment
|
It appears the Karmic repositories are no longer available.
Since they are for a previous version of Ubuntu, you might consider removing them from your sources list. Take a look at this help page for step-by-step.
add a comment
|
You can find the repositories under the "old-releases" server http://old-releases.ubuntu.com/ubuntu/dists/
And about how to edit the /etc/apt/sources.list
https://help.ubuntu.com/community/EOLUpgrades
Thanks gajdipajti, I'm looking for it inside the package list, but cannot find the correct ".deb". My ubuntu already has "libsensors3", but all the packages ask me for the "libsensors4". I know the normal solution should be upgrade, but I cannot do it because the computer is dedicated to be used with a software that only runs on 9.10.
– Rorro
Apr 13 '12 at 10:34
@Rorro: Which software only runs on Ubuntu 9.10?
– unforgettableid
Oct 9 '13 at 1:45
add a comment
|
There is an edge case - apt-get claims 16.04 LTS does not exist - where the old package (Vivid, in my case) was not in on the "old-releases" server. But apt-get could only find kernel and Google updates.
I am not sure exactly what my problem was because I had blindly followed the accepted answers sed
command (never a smart move).
This did not work because Vivid was not in the "old-releases" archive but was still on the gb.archive.ubuntu.com
mirror.
In that specific case, the solution was as follows:
sudo -i
edit /etc/apt/sources.list
Carefully go through all the sources and discover one of them was old and wrong and had failed to be properly updated (or something). Or, as I did, search replace from old-releases.ubuntu.com
to gb.archive.ubuntu.com
. It then upgraded, without a problem, to the next release while I caught up on some reading.
So either:
- There was a fault in my sources
- The
gb.archive.unbuntu.com
mirror has an older set of releases.
The takeaway here is that while the majority of answers here may apply in some cases it would pay to be sure that your /etc/apt/sources.list
is correct before you nuke it for the "old-releases" archive.
You can figure out which of the archive or your mirror has the version you need by simply pointing a browser tab at the archive and question and looking for your version name in the folder list. Whichever one has your version, is the source you need to use.
add a comment
|
9 Answers
9
active
oldest
votes
9 Answers
9
active
oldest
votes
active
oldest
votes
active
oldest
votes
The repositories for older releases that are not supported (like 11.04, 11.10 and 13.04) get moved to an archive server. There are repositories available at http://old-releases.ubuntu.com.
The reason for this is that it is now out of support and no longer receiving updates and security patches.
I would urge you to consider a supported distribution. If your computer is too old in terms of memory or processor then you should consider a distribution such as Lubuntu or Xubuntu.
If you want to continue using an outdated release then edit /etc/apt/sources.list
and change archive.ubuntu.com
and security.ubuntu.com
to old-releases.ubuntu.com
.
You can do this with sed
:
sudo sed -i -re 's/([a-z]2.)?archive.ubuntu.com|security.ubuntu.com/old-releases.ubuntu.com/g' /etc/apt/sources.list
then update with:
sudo apt-get update && sudo apt-get dist-upgrade
Sometimes, it might be faster to create backups of your system and reinstall using supported release instead.
Source: Can I keep using Ubuntu 9.04 if it's outdated?
To upgrade to a new release:
Once you have performed the above steps to switch to the old-releases mirrors, update the Update Manager and then do do-release-upgrade
:
sudo apt-get update
sudo apt-get install update-manager-core
sudo do-release-upgrade
See also EOLUpgrades - Community Help Wiki.
9
and, just for the sake of completeness... what aboutextras
repository (for Skype etc)? Are they available anywhere after EOF?
– MestreLion
Apr 27 '13 at 1:00
2
an easier way issudo vi /etc/apt/sources.list
and modify it manually. I had to do it because I'm quite new and I don't know sed to make this work for karmic, Thanks, Your answer is still valid and correct.
– bhathiya-perera
Dec 3 '13 at 19:08
19
An even easier way issudo nano /etc/apt/sources.list
, asvi*
is just annoying...
– Wilf
Mar 1 '14 at 18:35
4
Thesed
command doesn't always work, as there are mirrors that are run by organizations outside ofubuntu.com
. I'm not even sure that there are three dots for all of the domain names. For those, you must manually edit/etc/apt/sources.list
.
– Olathe
Jul 9 '15 at 5:06
3
There is an issue with this in upgrading from 15.04 as of 3/21/17. Vivid is no longer supported, however the dist is not on old-releases.
– Matthew Titsworth
Mar 21 '17 at 20:07
|
show 4 more comments
The repositories for older releases that are not supported (like 11.04, 11.10 and 13.04) get moved to an archive server. There are repositories available at http://old-releases.ubuntu.com.
The reason for this is that it is now out of support and no longer receiving updates and security patches.
I would urge you to consider a supported distribution. If your computer is too old in terms of memory or processor then you should consider a distribution such as Lubuntu or Xubuntu.
If you want to continue using an outdated release then edit /etc/apt/sources.list
and change archive.ubuntu.com
and security.ubuntu.com
to old-releases.ubuntu.com
.
You can do this with sed
:
sudo sed -i -re 's/([a-z]2.)?archive.ubuntu.com|security.ubuntu.com/old-releases.ubuntu.com/g' /etc/apt/sources.list
then update with:
sudo apt-get update && sudo apt-get dist-upgrade
Sometimes, it might be faster to create backups of your system and reinstall using supported release instead.
Source: Can I keep using Ubuntu 9.04 if it's outdated?
To upgrade to a new release:
Once you have performed the above steps to switch to the old-releases mirrors, update the Update Manager and then do do-release-upgrade
:
sudo apt-get update
sudo apt-get install update-manager-core
sudo do-release-upgrade
See also EOLUpgrades - Community Help Wiki.
9
and, just for the sake of completeness... what aboutextras
repository (for Skype etc)? Are they available anywhere after EOF?
– MestreLion
Apr 27 '13 at 1:00
2
an easier way issudo vi /etc/apt/sources.list
and modify it manually. I had to do it because I'm quite new and I don't know sed to make this work for karmic, Thanks, Your answer is still valid and correct.
– bhathiya-perera
Dec 3 '13 at 19:08
19
An even easier way issudo nano /etc/apt/sources.list
, asvi*
is just annoying...
– Wilf
Mar 1 '14 at 18:35
4
Thesed
command doesn't always work, as there are mirrors that are run by organizations outside ofubuntu.com
. I'm not even sure that there are three dots for all of the domain names. For those, you must manually edit/etc/apt/sources.list
.
– Olathe
Jul 9 '15 at 5:06
3
There is an issue with this in upgrading from 15.04 as of 3/21/17. Vivid is no longer supported, however the dist is not on old-releases.
– Matthew Titsworth
Mar 21 '17 at 20:07
|
show 4 more comments
The repositories for older releases that are not supported (like 11.04, 11.10 and 13.04) get moved to an archive server. There are repositories available at http://old-releases.ubuntu.com.
The reason for this is that it is now out of support and no longer receiving updates and security patches.
I would urge you to consider a supported distribution. If your computer is too old in terms of memory or processor then you should consider a distribution such as Lubuntu or Xubuntu.
If you want to continue using an outdated release then edit /etc/apt/sources.list
and change archive.ubuntu.com
and security.ubuntu.com
to old-releases.ubuntu.com
.
You can do this with sed
:
sudo sed -i -re 's/([a-z]2.)?archive.ubuntu.com|security.ubuntu.com/old-releases.ubuntu.com/g' /etc/apt/sources.list
then update with:
sudo apt-get update && sudo apt-get dist-upgrade
Sometimes, it might be faster to create backups of your system and reinstall using supported release instead.
Source: Can I keep using Ubuntu 9.04 if it's outdated?
To upgrade to a new release:
Once you have performed the above steps to switch to the old-releases mirrors, update the Update Manager and then do do-release-upgrade
:
sudo apt-get update
sudo apt-get install update-manager-core
sudo do-release-upgrade
See also EOLUpgrades - Community Help Wiki.
The repositories for older releases that are not supported (like 11.04, 11.10 and 13.04) get moved to an archive server. There are repositories available at http://old-releases.ubuntu.com.
The reason for this is that it is now out of support and no longer receiving updates and security patches.
I would urge you to consider a supported distribution. If your computer is too old in terms of memory or processor then you should consider a distribution such as Lubuntu or Xubuntu.
If you want to continue using an outdated release then edit /etc/apt/sources.list
and change archive.ubuntu.com
and security.ubuntu.com
to old-releases.ubuntu.com
.
You can do this with sed
:
sudo sed -i -re 's/([a-z]2.)?archive.ubuntu.com|security.ubuntu.com/old-releases.ubuntu.com/g' /etc/apt/sources.list
then update with:
sudo apt-get update && sudo apt-get dist-upgrade
Sometimes, it might be faster to create backups of your system and reinstall using supported release instead.
Source: Can I keep using Ubuntu 9.04 if it's outdated?
To upgrade to a new release:
Once you have performed the above steps to switch to the old-releases mirrors, update the Update Manager and then do do-release-upgrade
:
sudo apt-get update
sudo apt-get install update-manager-core
sudo do-release-upgrade
See also EOLUpgrades - Community Help Wiki.
edited Feb 18 '18 at 12:47
dessert
30.6k7 gold badges89 silver badges124 bronze badges
30.6k7 gold badges89 silver badges124 bronze badges
answered Dec 31 '11 at 18:54
fossfreedom♦fossfreedom
156k40 gold badges345 silver badges388 bronze badges
156k40 gold badges345 silver badges388 bronze badges
9
and, just for the sake of completeness... what aboutextras
repository (for Skype etc)? Are they available anywhere after EOF?
– MestreLion
Apr 27 '13 at 1:00
2
an easier way issudo vi /etc/apt/sources.list
and modify it manually. I had to do it because I'm quite new and I don't know sed to make this work for karmic, Thanks, Your answer is still valid and correct.
– bhathiya-perera
Dec 3 '13 at 19:08
19
An even easier way issudo nano /etc/apt/sources.list
, asvi*
is just annoying...
– Wilf
Mar 1 '14 at 18:35
4
Thesed
command doesn't always work, as there are mirrors that are run by organizations outside ofubuntu.com
. I'm not even sure that there are three dots for all of the domain names. For those, you must manually edit/etc/apt/sources.list
.
– Olathe
Jul 9 '15 at 5:06
3
There is an issue with this in upgrading from 15.04 as of 3/21/17. Vivid is no longer supported, however the dist is not on old-releases.
– Matthew Titsworth
Mar 21 '17 at 20:07
|
show 4 more comments
9
and, just for the sake of completeness... what aboutextras
repository (for Skype etc)? Are they available anywhere after EOF?
– MestreLion
Apr 27 '13 at 1:00
2
an easier way issudo vi /etc/apt/sources.list
and modify it manually. I had to do it because I'm quite new and I don't know sed to make this work for karmic, Thanks, Your answer is still valid and correct.
– bhathiya-perera
Dec 3 '13 at 19:08
19
An even easier way issudo nano /etc/apt/sources.list
, asvi*
is just annoying...
– Wilf
Mar 1 '14 at 18:35
4
Thesed
command doesn't always work, as there are mirrors that are run by organizations outside ofubuntu.com
. I'm not even sure that there are three dots for all of the domain names. For those, you must manually edit/etc/apt/sources.list
.
– Olathe
Jul 9 '15 at 5:06
3
There is an issue with this in upgrading from 15.04 as of 3/21/17. Vivid is no longer supported, however the dist is not on old-releases.
– Matthew Titsworth
Mar 21 '17 at 20:07
9
9
and, just for the sake of completeness... what about
extras
repository (for Skype etc)? Are they available anywhere after EOF?– MestreLion
Apr 27 '13 at 1:00
and, just for the sake of completeness... what about
extras
repository (for Skype etc)? Are they available anywhere after EOF?– MestreLion
Apr 27 '13 at 1:00
2
2
an easier way is
sudo vi /etc/apt/sources.list
and modify it manually. I had to do it because I'm quite new and I don't know sed to make this work for karmic, Thanks, Your answer is still valid and correct.– bhathiya-perera
Dec 3 '13 at 19:08
an easier way is
sudo vi /etc/apt/sources.list
and modify it manually. I had to do it because I'm quite new and I don't know sed to make this work for karmic, Thanks, Your answer is still valid and correct.– bhathiya-perera
Dec 3 '13 at 19:08
19
19
An even easier way is
sudo nano /etc/apt/sources.list
, as vi*
is just annoying...– Wilf
Mar 1 '14 at 18:35
An even easier way is
sudo nano /etc/apt/sources.list
, as vi*
is just annoying...– Wilf
Mar 1 '14 at 18:35
4
4
The
sed
command doesn't always work, as there are mirrors that are run by organizations outside of ubuntu.com
. I'm not even sure that there are three dots for all of the domain names. For those, you must manually edit /etc/apt/sources.list
.– Olathe
Jul 9 '15 at 5:06
The
sed
command doesn't always work, as there are mirrors that are run by organizations outside of ubuntu.com
. I'm not even sure that there are three dots for all of the domain names. For those, you must manually edit /etc/apt/sources.list
.– Olathe
Jul 9 '15 at 5:06
3
3
There is an issue with this in upgrading from 15.04 as of 3/21/17. Vivid is no longer supported, however the dist is not on old-releases.
– Matthew Titsworth
Mar 21 '17 at 20:07
There is an issue with this in upgrading from 15.04 as of 3/21/17. Vivid is no longer supported, however the dist is not on old-releases.
– Matthew Titsworth
Mar 21 '17 at 20:07
|
show 4 more comments
What are 404 errors
The 404 or Not Found error message is a HTTP standard response code
indicating that the client was able to communicate with the server,
but the server could not find what was requested.
The web site hosting server will typically generate "404 - Page Not
Found" web page, when users attempts to follow a broken or dead link.
Why are we facing 404 errors
Ubuntu follows the approach of two different release cycles:
Normal Ubuntu releases are supported for 9 months. LTS releases are supported for 5 years.
Past releases may have different support schedules (for example, normal releases (before 13.04) used to be supported for 18 months, while LTS releases (before 12.04) used to be supported for 3 years on the desktop and 5 years on the server).
EOL: Once the support period for a particular release is over; they are called End Of Life (EOL) and all the updates and package repositories for that Release are transferred to a different server which results in 404 errors while running sudo apt-get update
. You can confirm if your release has become EOL by going to this page. If your Ubuntu release is mentioned under "End Of Life (EOL)" Table, then the release is no longer supported and you should try to upgrade to a newer supported release. However, if you wish to continue using this unsupported release, you would have to make necessary modifications in /etc/apt/sources.list
to point to the old-releases
server of Ubuntu.
Steps to make necessary modifications
Open your Terminal:
- Press Ctrl + Alt + T; OR
- If you have Gnome:
Applications
→Accessories
→Terminal
; OR - If you have Unity: press Super (the key between Left Ctrl and Left Alt) and query for
Terminal
.
Run the following command to enter into root shell:
sudo -i
input your user password and press Enter. The prompt would change and would indicate that the root user is now logged in. Here run the following command:
gedit /etc/apt/sources.list
The file would open in a new Gedit window. Find the first line which doesn't start with
#
. Suppose you are running Karmic Koala (Ubuntu 9.10): it should be like the following line:deb <siteurl> karmic main restricted
where,
<siteurl>
is your preferred server -http://gb.archive.ubuntu.com/ubuntu
in your case (for example).Press Ctrl + H to replace your
<siteurl>
withhttp://old-releases.ubuntu.com/ubuntu
.- Search for:
http://gb.archive.ubuntu.com/ubuntu
ie;<siteurl>
- Replace with:
http://old-releases.ubuntu.com/ubuntu
and - Press Replace All
- Search for:
Once again:
- Search for:
http://security.ubuntu.com/ubuntu
(this exact url for all the Ubuntu Releases — whatever be the present server that you are using) - Replace with:
http://old-releases.ubuntu.com/ubuntu
- Press Replace All
- Search for:
Save your file and exit Gedit.
Run the following command to get out of root shell:
logout
You would find that the prompt switches back to indicate that your normal user is now logged in. Then run the following:
sudo apt-get update
There you go. No 404 Errors this time. You can now install all the available packages for your Ubuntu Release. You can also run sudo apt-get dist-upgrade
to install any Security/Bug-fix updates which have not yet been installed but you won't get any further Security/Bug-fix updates from Ubuntu.
6
+1 for also including instructions to update the security repo.
– Gaffi
Mar 16 '13 at 16:07
Actually the first line without a # wasraring main restricted
, no deb whatsoever. I changed it as specified, and then also replaced the urls, but still got 404s.
– Yokhen
Oct 23 '14 at 23:11
2
@Yokhen If the line didn't begin withdeb <siteurl>
, then most likely your/etc/apt/sources.list
file has become corrupted due to some reason. Please follow the answers given at: How do I restore the default repositories?. That would restore the correct/etc/apt/sources.list
for you and then follow my answer to change the servers to point to the old-releases server.
– Aditya
Oct 24 '14 at 8:15
thanks! Somehow I managed to upgrade from 13.04 to 13.10 though, and now I'm on my way to 14.04.
– Yokhen
Oct 24 '14 at 8:56
1
@Dan, modified the answer, now we enter into root shell and then run the graphical program. No need to use gksudo anymore. I want to keep this answer for the novice users like me and don't want to complicate matters with using terminal based editors, however easy or powerful they may be.
– Aditya
Jul 17 '16 at 13:56
|
show 4 more comments
What are 404 errors
The 404 or Not Found error message is a HTTP standard response code
indicating that the client was able to communicate with the server,
but the server could not find what was requested.
The web site hosting server will typically generate "404 - Page Not
Found" web page, when users attempts to follow a broken or dead link.
Why are we facing 404 errors
Ubuntu follows the approach of two different release cycles:
Normal Ubuntu releases are supported for 9 months. LTS releases are supported for 5 years.
Past releases may have different support schedules (for example, normal releases (before 13.04) used to be supported for 18 months, while LTS releases (before 12.04) used to be supported for 3 years on the desktop and 5 years on the server).
EOL: Once the support period for a particular release is over; they are called End Of Life (EOL) and all the updates and package repositories for that Release are transferred to a different server which results in 404 errors while running sudo apt-get update
. You can confirm if your release has become EOL by going to this page. If your Ubuntu release is mentioned under "End Of Life (EOL)" Table, then the release is no longer supported and you should try to upgrade to a newer supported release. However, if you wish to continue using this unsupported release, you would have to make necessary modifications in /etc/apt/sources.list
to point to the old-releases
server of Ubuntu.
Steps to make necessary modifications
Open your Terminal:
- Press Ctrl + Alt + T; OR
- If you have Gnome:
Applications
→Accessories
→Terminal
; OR - If you have Unity: press Super (the key between Left Ctrl and Left Alt) and query for
Terminal
.
Run the following command to enter into root shell:
sudo -i
input your user password and press Enter. The prompt would change and would indicate that the root user is now logged in. Here run the following command:
gedit /etc/apt/sources.list
The file would open in a new Gedit window. Find the first line which doesn't start with
#
. Suppose you are running Karmic Koala (Ubuntu 9.10): it should be like the following line:deb <siteurl> karmic main restricted
where,
<siteurl>
is your preferred server -http://gb.archive.ubuntu.com/ubuntu
in your case (for example).Press Ctrl + H to replace your
<siteurl>
withhttp://old-releases.ubuntu.com/ubuntu
.- Search for:
http://gb.archive.ubuntu.com/ubuntu
ie;<siteurl>
- Replace with:
http://old-releases.ubuntu.com/ubuntu
and - Press Replace All
- Search for:
Once again:
- Search for:
http://security.ubuntu.com/ubuntu
(this exact url for all the Ubuntu Releases — whatever be the present server that you are using) - Replace with:
http://old-releases.ubuntu.com/ubuntu
- Press Replace All
- Search for:
Save your file and exit Gedit.
Run the following command to get out of root shell:
logout
You would find that the prompt switches back to indicate that your normal user is now logged in. Then run the following:
sudo apt-get update
There you go. No 404 Errors this time. You can now install all the available packages for your Ubuntu Release. You can also run sudo apt-get dist-upgrade
to install any Security/Bug-fix updates which have not yet been installed but you won't get any further Security/Bug-fix updates from Ubuntu.
6
+1 for also including instructions to update the security repo.
– Gaffi
Mar 16 '13 at 16:07
Actually the first line without a # wasraring main restricted
, no deb whatsoever. I changed it as specified, and then also replaced the urls, but still got 404s.
– Yokhen
Oct 23 '14 at 23:11
2
@Yokhen If the line didn't begin withdeb <siteurl>
, then most likely your/etc/apt/sources.list
file has become corrupted due to some reason. Please follow the answers given at: How do I restore the default repositories?. That would restore the correct/etc/apt/sources.list
for you and then follow my answer to change the servers to point to the old-releases server.
– Aditya
Oct 24 '14 at 8:15
thanks! Somehow I managed to upgrade from 13.04 to 13.10 though, and now I'm on my way to 14.04.
– Yokhen
Oct 24 '14 at 8:56
1
@Dan, modified the answer, now we enter into root shell and then run the graphical program. No need to use gksudo anymore. I want to keep this answer for the novice users like me and don't want to complicate matters with using terminal based editors, however easy or powerful they may be.
– Aditya
Jul 17 '16 at 13:56
|
show 4 more comments
What are 404 errors
The 404 or Not Found error message is a HTTP standard response code
indicating that the client was able to communicate with the server,
but the server could not find what was requested.
The web site hosting server will typically generate "404 - Page Not
Found" web page, when users attempts to follow a broken or dead link.
Why are we facing 404 errors
Ubuntu follows the approach of two different release cycles:
Normal Ubuntu releases are supported for 9 months. LTS releases are supported for 5 years.
Past releases may have different support schedules (for example, normal releases (before 13.04) used to be supported for 18 months, while LTS releases (before 12.04) used to be supported for 3 years on the desktop and 5 years on the server).
EOL: Once the support period for a particular release is over; they are called End Of Life (EOL) and all the updates and package repositories for that Release are transferred to a different server which results in 404 errors while running sudo apt-get update
. You can confirm if your release has become EOL by going to this page. If your Ubuntu release is mentioned under "End Of Life (EOL)" Table, then the release is no longer supported and you should try to upgrade to a newer supported release. However, if you wish to continue using this unsupported release, you would have to make necessary modifications in /etc/apt/sources.list
to point to the old-releases
server of Ubuntu.
Steps to make necessary modifications
Open your Terminal:
- Press Ctrl + Alt + T; OR
- If you have Gnome:
Applications
→Accessories
→Terminal
; OR - If you have Unity: press Super (the key between Left Ctrl and Left Alt) and query for
Terminal
.
Run the following command to enter into root shell:
sudo -i
input your user password and press Enter. The prompt would change and would indicate that the root user is now logged in. Here run the following command:
gedit /etc/apt/sources.list
The file would open in a new Gedit window. Find the first line which doesn't start with
#
. Suppose you are running Karmic Koala (Ubuntu 9.10): it should be like the following line:deb <siteurl> karmic main restricted
where,
<siteurl>
is your preferred server -http://gb.archive.ubuntu.com/ubuntu
in your case (for example).Press Ctrl + H to replace your
<siteurl>
withhttp://old-releases.ubuntu.com/ubuntu
.- Search for:
http://gb.archive.ubuntu.com/ubuntu
ie;<siteurl>
- Replace with:
http://old-releases.ubuntu.com/ubuntu
and - Press Replace All
- Search for:
Once again:
- Search for:
http://security.ubuntu.com/ubuntu
(this exact url for all the Ubuntu Releases — whatever be the present server that you are using) - Replace with:
http://old-releases.ubuntu.com/ubuntu
- Press Replace All
- Search for:
Save your file and exit Gedit.
Run the following command to get out of root shell:
logout
You would find that the prompt switches back to indicate that your normal user is now logged in. Then run the following:
sudo apt-get update
There you go. No 404 Errors this time. You can now install all the available packages for your Ubuntu Release. You can also run sudo apt-get dist-upgrade
to install any Security/Bug-fix updates which have not yet been installed but you won't get any further Security/Bug-fix updates from Ubuntu.
What are 404 errors
The 404 or Not Found error message is a HTTP standard response code
indicating that the client was able to communicate with the server,
but the server could not find what was requested.
The web site hosting server will typically generate "404 - Page Not
Found" web page, when users attempts to follow a broken or dead link.
Why are we facing 404 errors
Ubuntu follows the approach of two different release cycles:
Normal Ubuntu releases are supported for 9 months. LTS releases are supported for 5 years.
Past releases may have different support schedules (for example, normal releases (before 13.04) used to be supported for 18 months, while LTS releases (before 12.04) used to be supported for 3 years on the desktop and 5 years on the server).
EOL: Once the support period for a particular release is over; they are called End Of Life (EOL) and all the updates and package repositories for that Release are transferred to a different server which results in 404 errors while running sudo apt-get update
. You can confirm if your release has become EOL by going to this page. If your Ubuntu release is mentioned under "End Of Life (EOL)" Table, then the release is no longer supported and you should try to upgrade to a newer supported release. However, if you wish to continue using this unsupported release, you would have to make necessary modifications in /etc/apt/sources.list
to point to the old-releases
server of Ubuntu.
Steps to make necessary modifications
Open your Terminal:
- Press Ctrl + Alt + T; OR
- If you have Gnome:
Applications
→Accessories
→Terminal
; OR - If you have Unity: press Super (the key between Left Ctrl and Left Alt) and query for
Terminal
.
Run the following command to enter into root shell:
sudo -i
input your user password and press Enter. The prompt would change and would indicate that the root user is now logged in. Here run the following command:
gedit /etc/apt/sources.list
The file would open in a new Gedit window. Find the first line which doesn't start with
#
. Suppose you are running Karmic Koala (Ubuntu 9.10): it should be like the following line:deb <siteurl> karmic main restricted
where,
<siteurl>
is your preferred server -http://gb.archive.ubuntu.com/ubuntu
in your case (for example).Press Ctrl + H to replace your
<siteurl>
withhttp://old-releases.ubuntu.com/ubuntu
.- Search for:
http://gb.archive.ubuntu.com/ubuntu
ie;<siteurl>
- Replace with:
http://old-releases.ubuntu.com/ubuntu
and - Press Replace All
- Search for:
Once again:
- Search for:
http://security.ubuntu.com/ubuntu
(this exact url for all the Ubuntu Releases — whatever be the present server that you are using) - Replace with:
http://old-releases.ubuntu.com/ubuntu
- Press Replace All
- Search for:
Save your file and exit Gedit.
Run the following command to get out of root shell:
logout
You would find that the prompt switches back to indicate that your normal user is now logged in. Then run the following:
sudo apt-get update
There you go. No 404 Errors this time. You can now install all the available packages for your Ubuntu Release. You can also run sudo apt-get dist-upgrade
to install any Security/Bug-fix updates which have not yet been installed but you won't get any further Security/Bug-fix updates from Ubuntu.
edited Jul 17 '16 at 13:54
answered Jan 6 '13 at 23:02
AdityaAditya
11.5k14 gold badges58 silver badges90 bronze badges
11.5k14 gold badges58 silver badges90 bronze badges
6
+1 for also including instructions to update the security repo.
– Gaffi
Mar 16 '13 at 16:07
Actually the first line without a # wasraring main restricted
, no deb whatsoever. I changed it as specified, and then also replaced the urls, but still got 404s.
– Yokhen
Oct 23 '14 at 23:11
2
@Yokhen If the line didn't begin withdeb <siteurl>
, then most likely your/etc/apt/sources.list
file has become corrupted due to some reason. Please follow the answers given at: How do I restore the default repositories?. That would restore the correct/etc/apt/sources.list
for you and then follow my answer to change the servers to point to the old-releases server.
– Aditya
Oct 24 '14 at 8:15
thanks! Somehow I managed to upgrade from 13.04 to 13.10 though, and now I'm on my way to 14.04.
– Yokhen
Oct 24 '14 at 8:56
1
@Dan, modified the answer, now we enter into root shell and then run the graphical program. No need to use gksudo anymore. I want to keep this answer for the novice users like me and don't want to complicate matters with using terminal based editors, however easy or powerful they may be.
– Aditya
Jul 17 '16 at 13:56
|
show 4 more comments
6
+1 for also including instructions to update the security repo.
– Gaffi
Mar 16 '13 at 16:07
Actually the first line without a # wasraring main restricted
, no deb whatsoever. I changed it as specified, and then also replaced the urls, but still got 404s.
– Yokhen
Oct 23 '14 at 23:11
2
@Yokhen If the line didn't begin withdeb <siteurl>
, then most likely your/etc/apt/sources.list
file has become corrupted due to some reason. Please follow the answers given at: How do I restore the default repositories?. That would restore the correct/etc/apt/sources.list
for you and then follow my answer to change the servers to point to the old-releases server.
– Aditya
Oct 24 '14 at 8:15
thanks! Somehow I managed to upgrade from 13.04 to 13.10 though, and now I'm on my way to 14.04.
– Yokhen
Oct 24 '14 at 8:56
1
@Dan, modified the answer, now we enter into root shell and then run the graphical program. No need to use gksudo anymore. I want to keep this answer for the novice users like me and don't want to complicate matters with using terminal based editors, however easy or powerful they may be.
– Aditya
Jul 17 '16 at 13:56
6
6
+1 for also including instructions to update the security repo.
– Gaffi
Mar 16 '13 at 16:07
+1 for also including instructions to update the security repo.
– Gaffi
Mar 16 '13 at 16:07
Actually the first line without a # was
raring main restricted
, no deb whatsoever. I changed it as specified, and then also replaced the urls, but still got 404s.– Yokhen
Oct 23 '14 at 23:11
Actually the first line without a # was
raring main restricted
, no deb whatsoever. I changed it as specified, and then also replaced the urls, but still got 404s.– Yokhen
Oct 23 '14 at 23:11
2
2
@Yokhen If the line didn't begin with
deb <siteurl>
, then most likely your /etc/apt/sources.list
file has become corrupted due to some reason. Please follow the answers given at: How do I restore the default repositories?. That would restore the correct /etc/apt/sources.list
for you and then follow my answer to change the servers to point to the old-releases server.– Aditya
Oct 24 '14 at 8:15
@Yokhen If the line didn't begin with
deb <siteurl>
, then most likely your /etc/apt/sources.list
file has become corrupted due to some reason. Please follow the answers given at: How do I restore the default repositories?. That would restore the correct /etc/apt/sources.list
for you and then follow my answer to change the servers to point to the old-releases server.– Aditya
Oct 24 '14 at 8:15
thanks! Somehow I managed to upgrade from 13.04 to 13.10 though, and now I'm on my way to 14.04.
– Yokhen
Oct 24 '14 at 8:56
thanks! Somehow I managed to upgrade from 13.04 to 13.10 though, and now I'm on my way to 14.04.
– Yokhen
Oct 24 '14 at 8:56
1
1
@Dan, modified the answer, now we enter into root shell and then run the graphical program. No need to use gksudo anymore. I want to keep this answer for the novice users like me and don't want to complicate matters with using terminal based editors, however easy or powerful they may be.
– Aditya
Jul 17 '16 at 13:56
@Dan, modified the answer, now we enter into root shell and then run the graphical program. No need to use gksudo anymore. I want to keep this answer for the novice users like me and don't want to complicate matters with using terminal based editors, however easy or powerful they may be.
– Aditya
Jul 17 '16 at 13:56
|
show 4 more comments
The short answer is to add the next apt repository to the Third-Party Software (or Other Software in newer versions) in Software Sources (or Software & Updates in newer versions):
deb http://old-releases.ubuntu.com/ubuntu code_name main restricted universe multiverse
The long answer...
GUI Method
Well, actually we will do this without to use any terminal. Not even once. Just GUI, I promise ;-)
First, open Software Sources (or Software & Updates in newer versions). It does not matter how old is your Ubuntu, there is certainly something like this. For Ubuntu 9.04 (Jaunty Jackalope) look at next image to see where is located:
After Software Sources (or Software & Updates) it is open, go in Ubuntu Software and Updates tabs and unselect everytiyng like in next pictures. You don't need this things anymore since your Ubuntu version is End of Life:
Without closing Software Sources (or Software & Updates), go in Third-Party Software (for newest releases this tab is named Other Software) tab and add a new apt repository. Insert exactly next line when you are asked:
deb http://old-releases.ubuntu.com/ubuntu jaunty main restricted universe multiverse
If your version of Ubuntu is other than 9.04, replace in the above line jaunty
with your Ubuntu codename (for example if you have Ubuntu 9.10, replace with karmic
and so on):
Now, when you will close Software Sources (or Software & Updates) you will be asked to reload the information about available software. Just be sure that you have a working internet connection:
And now you are free to download almost whatever you want. For 9.04 you can use Synaptic Package Manager. For newest releases there is Ubuntu Software Center.
For example to install VLC in Ubuntu 9.04 using Synaptic Package Manager, follow the instructions in the following pictures:
If you want to Update your Ubuntu to a new release, just go to System > Update Manager:
I tested this method from a live session of Ubuntu 9.04 (Jaunty Jackalope) and as you can see from these pictures it worked. If you are on an installed session of Ubuntu you will be asked sometimes for root or admin password. Just insert your personal user password when you are asked.
1
I just did all this from installed 10.10 (maverick) version. Everything well good as described. @Radu, your answer is flawless!
– Gediminas Jeremiah Gudelis
Aug 28 '13 at 20:01
1
Those images needs updating... wait... what are you doing with a pre-12.04?
– Braiam
Dec 30 '13 at 14:01
1
@Braiam Those images are up to date. If you will give a try to Ubuntu 9.04 (Jaunty Jackalope), you will understand.
– Radu Rădeanu
Mar 22 '14 at 19:49
1
@RaduRădeanu Ubuntu 9.04 was my first foray into the linux world. Ahh, those screenshots bring back memories!
– Tyzoid
Apr 13 '14 at 22:03
Cannot get this to work for 15.04 to be upgraded to 16.04. Can't get past adding the new APT line please help.
– MrMule
Oct 10 '16 at 18:34
|
show 1 more comment
The short answer is to add the next apt repository to the Third-Party Software (or Other Software in newer versions) in Software Sources (or Software & Updates in newer versions):
deb http://old-releases.ubuntu.com/ubuntu code_name main restricted universe multiverse
The long answer...
GUI Method
Well, actually we will do this without to use any terminal. Not even once. Just GUI, I promise ;-)
First, open Software Sources (or Software & Updates in newer versions). It does not matter how old is your Ubuntu, there is certainly something like this. For Ubuntu 9.04 (Jaunty Jackalope) look at next image to see where is located:
After Software Sources (or Software & Updates) it is open, go in Ubuntu Software and Updates tabs and unselect everytiyng like in next pictures. You don't need this things anymore since your Ubuntu version is End of Life:
Without closing Software Sources (or Software & Updates), go in Third-Party Software (for newest releases this tab is named Other Software) tab and add a new apt repository. Insert exactly next line when you are asked:
deb http://old-releases.ubuntu.com/ubuntu jaunty main restricted universe multiverse
If your version of Ubuntu is other than 9.04, replace in the above line jaunty
with your Ubuntu codename (for example if you have Ubuntu 9.10, replace with karmic
and so on):
Now, when you will close Software Sources (or Software & Updates) you will be asked to reload the information about available software. Just be sure that you have a working internet connection:
And now you are free to download almost whatever you want. For 9.04 you can use Synaptic Package Manager. For newest releases there is Ubuntu Software Center.
For example to install VLC in Ubuntu 9.04 using Synaptic Package Manager, follow the instructions in the following pictures:
If you want to Update your Ubuntu to a new release, just go to System > Update Manager:
I tested this method from a live session of Ubuntu 9.04 (Jaunty Jackalope) and as you can see from these pictures it worked. If you are on an installed session of Ubuntu you will be asked sometimes for root or admin password. Just insert your personal user password when you are asked.
1
I just did all this from installed 10.10 (maverick) version. Everything well good as described. @Radu, your answer is flawless!
– Gediminas Jeremiah Gudelis
Aug 28 '13 at 20:01
1
Those images needs updating... wait... what are you doing with a pre-12.04?
– Braiam
Dec 30 '13 at 14:01
1
@Braiam Those images are up to date. If you will give a try to Ubuntu 9.04 (Jaunty Jackalope), you will understand.
– Radu Rădeanu
Mar 22 '14 at 19:49
1
@RaduRădeanu Ubuntu 9.04 was my first foray into the linux world. Ahh, those screenshots bring back memories!
– Tyzoid
Apr 13 '14 at 22:03
Cannot get this to work for 15.04 to be upgraded to 16.04. Can't get past adding the new APT line please help.
– MrMule
Oct 10 '16 at 18:34
|
show 1 more comment
The short answer is to add the next apt repository to the Third-Party Software (or Other Software in newer versions) in Software Sources (or Software & Updates in newer versions):
deb http://old-releases.ubuntu.com/ubuntu code_name main restricted universe multiverse
The long answer...
GUI Method
Well, actually we will do this without to use any terminal. Not even once. Just GUI, I promise ;-)
First, open Software Sources (or Software & Updates in newer versions). It does not matter how old is your Ubuntu, there is certainly something like this. For Ubuntu 9.04 (Jaunty Jackalope) look at next image to see where is located:
After Software Sources (or Software & Updates) it is open, go in Ubuntu Software and Updates tabs and unselect everytiyng like in next pictures. You don't need this things anymore since your Ubuntu version is End of Life:
Without closing Software Sources (or Software & Updates), go in Third-Party Software (for newest releases this tab is named Other Software) tab and add a new apt repository. Insert exactly next line when you are asked:
deb http://old-releases.ubuntu.com/ubuntu jaunty main restricted universe multiverse
If your version of Ubuntu is other than 9.04, replace in the above line jaunty
with your Ubuntu codename (for example if you have Ubuntu 9.10, replace with karmic
and so on):
Now, when you will close Software Sources (or Software & Updates) you will be asked to reload the information about available software. Just be sure that you have a working internet connection:
And now you are free to download almost whatever you want. For 9.04 you can use Synaptic Package Manager. For newest releases there is Ubuntu Software Center.
For example to install VLC in Ubuntu 9.04 using Synaptic Package Manager, follow the instructions in the following pictures:
If you want to Update your Ubuntu to a new release, just go to System > Update Manager:
I tested this method from a live session of Ubuntu 9.04 (Jaunty Jackalope) and as you can see from these pictures it worked. If you are on an installed session of Ubuntu you will be asked sometimes for root or admin password. Just insert your personal user password when you are asked.
The short answer is to add the next apt repository to the Third-Party Software (or Other Software in newer versions) in Software Sources (or Software & Updates in newer versions):
deb http://old-releases.ubuntu.com/ubuntu code_name main restricted universe multiverse
The long answer...
GUI Method
Well, actually we will do this without to use any terminal. Not even once. Just GUI, I promise ;-)
First, open Software Sources (or Software & Updates in newer versions). It does not matter how old is your Ubuntu, there is certainly something like this. For Ubuntu 9.04 (Jaunty Jackalope) look at next image to see where is located:
After Software Sources (or Software & Updates) it is open, go in Ubuntu Software and Updates tabs and unselect everytiyng like in next pictures. You don't need this things anymore since your Ubuntu version is End of Life:
Without closing Software Sources (or Software & Updates), go in Third-Party Software (for newest releases this tab is named Other Software) tab and add a new apt repository. Insert exactly next line when you are asked:
deb http://old-releases.ubuntu.com/ubuntu jaunty main restricted universe multiverse
If your version of Ubuntu is other than 9.04, replace in the above line jaunty
with your Ubuntu codename (for example if you have Ubuntu 9.10, replace with karmic
and so on):
Now, when you will close Software Sources (or Software & Updates) you will be asked to reload the information about available software. Just be sure that you have a working internet connection:
And now you are free to download almost whatever you want. For 9.04 you can use Synaptic Package Manager. For newest releases there is Ubuntu Software Center.
For example to install VLC in Ubuntu 9.04 using Synaptic Package Manager, follow the instructions in the following pictures:
If you want to Update your Ubuntu to a new release, just go to System > Update Manager:
I tested this method from a live session of Ubuntu 9.04 (Jaunty Jackalope) and as you can see from these pictures it worked. If you are on an installed session of Ubuntu you will be asked sometimes for root or admin password. Just insert your personal user password when you are asked.
edited Mar 22 '14 at 19:44
answered Jun 21 '13 at 11:24
Radu RădeanuRadu Rădeanu
132k38 gold badges277 silver badges345 bronze badges
132k38 gold badges277 silver badges345 bronze badges
1
I just did all this from installed 10.10 (maverick) version. Everything well good as described. @Radu, your answer is flawless!
– Gediminas Jeremiah Gudelis
Aug 28 '13 at 20:01
1
Those images needs updating... wait... what are you doing with a pre-12.04?
– Braiam
Dec 30 '13 at 14:01
1
@Braiam Those images are up to date. If you will give a try to Ubuntu 9.04 (Jaunty Jackalope), you will understand.
– Radu Rădeanu
Mar 22 '14 at 19:49
1
@RaduRădeanu Ubuntu 9.04 was my first foray into the linux world. Ahh, those screenshots bring back memories!
– Tyzoid
Apr 13 '14 at 22:03
Cannot get this to work for 15.04 to be upgraded to 16.04. Can't get past adding the new APT line please help.
– MrMule
Oct 10 '16 at 18:34
|
show 1 more comment
1
I just did all this from installed 10.10 (maverick) version. Everything well good as described. @Radu, your answer is flawless!
– Gediminas Jeremiah Gudelis
Aug 28 '13 at 20:01
1
Those images needs updating... wait... what are you doing with a pre-12.04?
– Braiam
Dec 30 '13 at 14:01
1
@Braiam Those images are up to date. If you will give a try to Ubuntu 9.04 (Jaunty Jackalope), you will understand.
– Radu Rădeanu
Mar 22 '14 at 19:49
1
@RaduRădeanu Ubuntu 9.04 was my first foray into the linux world. Ahh, those screenshots bring back memories!
– Tyzoid
Apr 13 '14 at 22:03
Cannot get this to work for 15.04 to be upgraded to 16.04. Can't get past adding the new APT line please help.
– MrMule
Oct 10 '16 at 18:34
1
1
I just did all this from installed 10.10 (maverick) version. Everything well good as described. @Radu, your answer is flawless!
– Gediminas Jeremiah Gudelis
Aug 28 '13 at 20:01
I just did all this from installed 10.10 (maverick) version. Everything well good as described. @Radu, your answer is flawless!
– Gediminas Jeremiah Gudelis
Aug 28 '13 at 20:01
1
1
Those images needs updating... wait... what are you doing with a pre-12.04?
– Braiam
Dec 30 '13 at 14:01
Those images needs updating... wait... what are you doing with a pre-12.04?
– Braiam
Dec 30 '13 at 14:01
1
1
@Braiam Those images are up to date. If you will give a try to Ubuntu 9.04 (Jaunty Jackalope), you will understand.
– Radu Rădeanu
Mar 22 '14 at 19:49
@Braiam Those images are up to date. If you will give a try to Ubuntu 9.04 (Jaunty Jackalope), you will understand.
– Radu Rădeanu
Mar 22 '14 at 19:49
1
1
@RaduRădeanu Ubuntu 9.04 was my first foray into the linux world. Ahh, those screenshots bring back memories!
– Tyzoid
Apr 13 '14 at 22:03
@RaduRădeanu Ubuntu 9.04 was my first foray into the linux world. Ahh, those screenshots bring back memories!
– Tyzoid
Apr 13 '14 at 22:03
Cannot get this to work for 15.04 to be upgraded to 16.04. Can't get past adding the new APT line please help.
– MrMule
Oct 10 '16 at 18:34
Cannot get this to work for 15.04 to be upgraded to 16.04. Can't get past adding the new APT line please help.
– MrMule
Oct 10 '16 at 18:34
|
show 1 more comment
I got here since I could not upgrade a system from 15.10 (EOL) to 16.04. But none of the answers worked for me... even after doing everything that was suggested here I kept getting from sudo do-release-upgrade
the annoying response:
Checking for a new Ubuntu release
No new release found
And I had no success in running update-manager
; it kept throwing exceptions which I could not resolve. I suspect something is corrupted in my 15.10 installation, but the bottom line is that the built-in upgrades just fail.
So I looked for a non-built-in method, and sure enough I found it looking at this answer.
Here is the solution that worked for me:
- Open http://changelogs.ubuntu.com/meta-release
- Locate the release you want to upgrade to. In my case it is Xenial Xerus (16.04 Long Term Support).
- Locate the UpgradeTool URL. For xenial it is this one. Download the tarball from that URL into an empty folder and and open it (
tar -xzf
or using the GUI). Locate the executable file with the same name as the distribution (in my case
xenial
). Run it withsudo
:sudo ./xenial &
Approve the upgrade, and wait for the download to complete - there's thousands of files and likely over a Gigabyte. Proceed with installing the upgrade...
(Edited long after I performed the upgrade... It was successful and I forgot to update)
Wait until it completes, approve if asked... I don't recall the exact details
After the reboot the new version is running successfully, and all updates can be fetched normally.
1
It took me a while to find this post. Only using the referenced tarball I succeeded in getting the upgrade running from 15.04 / wily. The approaches using the old-releases urls did not work. I hope this helps other users getting into this problem.
– Jeroen
Dec 19 '16 at 9:34
I'm glad you found it helpful!
– laugh
Dec 21 '16 at 19:35
1
Seriously thanks for this, I just used these steps to upgrade 10.04 to 12.04. My issue was different in that my install wasn't corrupted, but there was an error on do-release-upgrade which I was unable to find in the terminal. Following these steps popped up a dialog telling me "error authenticating some packages" which led me to askubuntu.com/a/426121/262601 which DID allow the upgrade to continue successfully. Was pulling my hair out, but its my own fault for not upgrading sooner.
– Fooxz
Jan 6 '17 at 0:27
Unfortunately, not even this works for 15.04
– MiroJanosik
Jan 22 '18 at 18:32
Works as a charm! I had a zesty server that i neglected and I got it to artful and could upgrade further from there, thanks!
– Patrick Cornelissen
Aug 6 '18 at 7:18
|
show 1 more comment
I got here since I could not upgrade a system from 15.10 (EOL) to 16.04. But none of the answers worked for me... even after doing everything that was suggested here I kept getting from sudo do-release-upgrade
the annoying response:
Checking for a new Ubuntu release
No new release found
And I had no success in running update-manager
; it kept throwing exceptions which I could not resolve. I suspect something is corrupted in my 15.10 installation, but the bottom line is that the built-in upgrades just fail.
So I looked for a non-built-in method, and sure enough I found it looking at this answer.
Here is the solution that worked for me:
- Open http://changelogs.ubuntu.com/meta-release
- Locate the release you want to upgrade to. In my case it is Xenial Xerus (16.04 Long Term Support).
- Locate the UpgradeTool URL. For xenial it is this one. Download the tarball from that URL into an empty folder and and open it (
tar -xzf
or using the GUI). Locate the executable file with the same name as the distribution (in my case
xenial
). Run it withsudo
:sudo ./xenial &
Approve the upgrade, and wait for the download to complete - there's thousands of files and likely over a Gigabyte. Proceed with installing the upgrade...
(Edited long after I performed the upgrade... It was successful and I forgot to update)
Wait until it completes, approve if asked... I don't recall the exact details
After the reboot the new version is running successfully, and all updates can be fetched normally.
1
It took me a while to find this post. Only using the referenced tarball I succeeded in getting the upgrade running from 15.04 / wily. The approaches using the old-releases urls did not work. I hope this helps other users getting into this problem.
– Jeroen
Dec 19 '16 at 9:34
I'm glad you found it helpful!
– laugh
Dec 21 '16 at 19:35
1
Seriously thanks for this, I just used these steps to upgrade 10.04 to 12.04. My issue was different in that my install wasn't corrupted, but there was an error on do-release-upgrade which I was unable to find in the terminal. Following these steps popped up a dialog telling me "error authenticating some packages" which led me to askubuntu.com/a/426121/262601 which DID allow the upgrade to continue successfully. Was pulling my hair out, but its my own fault for not upgrading sooner.
– Fooxz
Jan 6 '17 at 0:27
Unfortunately, not even this works for 15.04
– MiroJanosik
Jan 22 '18 at 18:32
Works as a charm! I had a zesty server that i neglected and I got it to artful and could upgrade further from there, thanks!
– Patrick Cornelissen
Aug 6 '18 at 7:18
|
show 1 more comment
I got here since I could not upgrade a system from 15.10 (EOL) to 16.04. But none of the answers worked for me... even after doing everything that was suggested here I kept getting from sudo do-release-upgrade
the annoying response:
Checking for a new Ubuntu release
No new release found
And I had no success in running update-manager
; it kept throwing exceptions which I could not resolve. I suspect something is corrupted in my 15.10 installation, but the bottom line is that the built-in upgrades just fail.
So I looked for a non-built-in method, and sure enough I found it looking at this answer.
Here is the solution that worked for me:
- Open http://changelogs.ubuntu.com/meta-release
- Locate the release you want to upgrade to. In my case it is Xenial Xerus (16.04 Long Term Support).
- Locate the UpgradeTool URL. For xenial it is this one. Download the tarball from that URL into an empty folder and and open it (
tar -xzf
or using the GUI). Locate the executable file with the same name as the distribution (in my case
xenial
). Run it withsudo
:sudo ./xenial &
Approve the upgrade, and wait for the download to complete - there's thousands of files and likely over a Gigabyte. Proceed with installing the upgrade...
(Edited long after I performed the upgrade... It was successful and I forgot to update)
Wait until it completes, approve if asked... I don't recall the exact details
After the reboot the new version is running successfully, and all updates can be fetched normally.
I got here since I could not upgrade a system from 15.10 (EOL) to 16.04. But none of the answers worked for me... even after doing everything that was suggested here I kept getting from sudo do-release-upgrade
the annoying response:
Checking for a new Ubuntu release
No new release found
And I had no success in running update-manager
; it kept throwing exceptions which I could not resolve. I suspect something is corrupted in my 15.10 installation, but the bottom line is that the built-in upgrades just fail.
So I looked for a non-built-in method, and sure enough I found it looking at this answer.
Here is the solution that worked for me:
- Open http://changelogs.ubuntu.com/meta-release
- Locate the release you want to upgrade to. In my case it is Xenial Xerus (16.04 Long Term Support).
- Locate the UpgradeTool URL. For xenial it is this one. Download the tarball from that URL into an empty folder and and open it (
tar -xzf
or using the GUI). Locate the executable file with the same name as the distribution (in my case
xenial
). Run it withsudo
:sudo ./xenial &
Approve the upgrade, and wait for the download to complete - there's thousands of files and likely over a Gigabyte. Proceed with installing the upgrade...
(Edited long after I performed the upgrade... It was successful and I forgot to update)
Wait until it completes, approve if asked... I don't recall the exact details
After the reboot the new version is running successfully, and all updates can be fetched normally.
edited May 14 '18 at 17:59
P0lT10n
1054 bronze badges
1054 bronze badges
answered Oct 15 '16 at 12:19
laughlaugh
7417 silver badges19 bronze badges
7417 silver badges19 bronze badges
1
It took me a while to find this post. Only using the referenced tarball I succeeded in getting the upgrade running from 15.04 / wily. The approaches using the old-releases urls did not work. I hope this helps other users getting into this problem.
– Jeroen
Dec 19 '16 at 9:34
I'm glad you found it helpful!
– laugh
Dec 21 '16 at 19:35
1
Seriously thanks for this, I just used these steps to upgrade 10.04 to 12.04. My issue was different in that my install wasn't corrupted, but there was an error on do-release-upgrade which I was unable to find in the terminal. Following these steps popped up a dialog telling me "error authenticating some packages" which led me to askubuntu.com/a/426121/262601 which DID allow the upgrade to continue successfully. Was pulling my hair out, but its my own fault for not upgrading sooner.
– Fooxz
Jan 6 '17 at 0:27
Unfortunately, not even this works for 15.04
– MiroJanosik
Jan 22 '18 at 18:32
Works as a charm! I had a zesty server that i neglected and I got it to artful and could upgrade further from there, thanks!
– Patrick Cornelissen
Aug 6 '18 at 7:18
|
show 1 more comment
1
It took me a while to find this post. Only using the referenced tarball I succeeded in getting the upgrade running from 15.04 / wily. The approaches using the old-releases urls did not work. I hope this helps other users getting into this problem.
– Jeroen
Dec 19 '16 at 9:34
I'm glad you found it helpful!
– laugh
Dec 21 '16 at 19:35
1
Seriously thanks for this, I just used these steps to upgrade 10.04 to 12.04. My issue was different in that my install wasn't corrupted, but there was an error on do-release-upgrade which I was unable to find in the terminal. Following these steps popped up a dialog telling me "error authenticating some packages" which led me to askubuntu.com/a/426121/262601 which DID allow the upgrade to continue successfully. Was pulling my hair out, but its my own fault for not upgrading sooner.
– Fooxz
Jan 6 '17 at 0:27
Unfortunately, not even this works for 15.04
– MiroJanosik
Jan 22 '18 at 18:32
Works as a charm! I had a zesty server that i neglected and I got it to artful and could upgrade further from there, thanks!
– Patrick Cornelissen
Aug 6 '18 at 7:18
1
1
It took me a while to find this post. Only using the referenced tarball I succeeded in getting the upgrade running from 15.04 / wily. The approaches using the old-releases urls did not work. I hope this helps other users getting into this problem.
– Jeroen
Dec 19 '16 at 9:34
It took me a while to find this post. Only using the referenced tarball I succeeded in getting the upgrade running from 15.04 / wily. The approaches using the old-releases urls did not work. I hope this helps other users getting into this problem.
– Jeroen
Dec 19 '16 at 9:34
I'm glad you found it helpful!
– laugh
Dec 21 '16 at 19:35
I'm glad you found it helpful!
– laugh
Dec 21 '16 at 19:35
1
1
Seriously thanks for this, I just used these steps to upgrade 10.04 to 12.04. My issue was different in that my install wasn't corrupted, but there was an error on do-release-upgrade which I was unable to find in the terminal. Following these steps popped up a dialog telling me "error authenticating some packages" which led me to askubuntu.com/a/426121/262601 which DID allow the upgrade to continue successfully. Was pulling my hair out, but its my own fault for not upgrading sooner.
– Fooxz
Jan 6 '17 at 0:27
Seriously thanks for this, I just used these steps to upgrade 10.04 to 12.04. My issue was different in that my install wasn't corrupted, but there was an error on do-release-upgrade which I was unable to find in the terminal. Following these steps popped up a dialog telling me "error authenticating some packages" which led me to askubuntu.com/a/426121/262601 which DID allow the upgrade to continue successfully. Was pulling my hair out, but its my own fault for not upgrading sooner.
– Fooxz
Jan 6 '17 at 0:27
Unfortunately, not even this works for 15.04
– MiroJanosik
Jan 22 '18 at 18:32
Unfortunately, not even this works for 15.04
– MiroJanosik
Jan 22 '18 at 18:32
Works as a charm! I had a zesty server that i neglected and I got it to artful and could upgrade further from there, thanks!
– Patrick Cornelissen
Aug 6 '18 at 7:18
Works as a charm! I had a zesty server that i neglected and I got it to artful and could upgrade further from there, thanks!
– Patrick Cornelissen
Aug 6 '18 at 7:18
|
show 1 more comment
To get apt-get
working again, change your software sources to the old release repositories.
gksudo gedit /etc/apt/sources.list
delete whatever is in there, and paste the following:
# Required
deb http://old-releases.ubuntu.com/ubuntu/ karmic main restricted universe multiverse
deb http://old-releases.ubuntu.com/ubuntu/ karmic-updates main restricted universe multiverse
deb http://old-releases.ubuntu.com/ubuntu/ karmic-security main restricted universe multiverse
# Optional
#deb http://old-releases.ubuntu.com/ubuntu/ karmic-backports main restricted universe multiverse
That's all.
Thanks mikewhatever, but the result is the same when I try "apt-get install lm-sensors". Maybe there's another missing source: "Reading package lists... Done Building dependency tree Reading state information... Done Package lm-sensors is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package lm-sensors has no installation candidate"
– Rorro
Apr 13 '12 at 10:55
Here are the debs: old-releases.ubuntu.com/ubuntu/pool/main/l/lm-sensors-3. I trust it, you've reloaded the sources list, right?
– mikewhatever
Apr 13 '12 at 12:08
This answer does not work... Why does it have so many upvotes? Did anybody actually test it?
– Tomáš Zato - Reinstate Monica
Aug 15 '14 at 11:00
I've tested it, but the real question is: Why are you still on Karmic? It's been out of support for years, and you should really move on to a more recent release.
– mikewhatever
Aug 15 '14 at 12:13
add a comment
|
To get apt-get
working again, change your software sources to the old release repositories.
gksudo gedit /etc/apt/sources.list
delete whatever is in there, and paste the following:
# Required
deb http://old-releases.ubuntu.com/ubuntu/ karmic main restricted universe multiverse
deb http://old-releases.ubuntu.com/ubuntu/ karmic-updates main restricted universe multiverse
deb http://old-releases.ubuntu.com/ubuntu/ karmic-security main restricted universe multiverse
# Optional
#deb http://old-releases.ubuntu.com/ubuntu/ karmic-backports main restricted universe multiverse
That's all.
Thanks mikewhatever, but the result is the same when I try "apt-get install lm-sensors". Maybe there's another missing source: "Reading package lists... Done Building dependency tree Reading state information... Done Package lm-sensors is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package lm-sensors has no installation candidate"
– Rorro
Apr 13 '12 at 10:55
Here are the debs: old-releases.ubuntu.com/ubuntu/pool/main/l/lm-sensors-3. I trust it, you've reloaded the sources list, right?
– mikewhatever
Apr 13 '12 at 12:08
This answer does not work... Why does it have so many upvotes? Did anybody actually test it?
– Tomáš Zato - Reinstate Monica
Aug 15 '14 at 11:00
I've tested it, but the real question is: Why are you still on Karmic? It's been out of support for years, and you should really move on to a more recent release.
– mikewhatever
Aug 15 '14 at 12:13
add a comment
|
To get apt-get
working again, change your software sources to the old release repositories.
gksudo gedit /etc/apt/sources.list
delete whatever is in there, and paste the following:
# Required
deb http://old-releases.ubuntu.com/ubuntu/ karmic main restricted universe multiverse
deb http://old-releases.ubuntu.com/ubuntu/ karmic-updates main restricted universe multiverse
deb http://old-releases.ubuntu.com/ubuntu/ karmic-security main restricted universe multiverse
# Optional
#deb http://old-releases.ubuntu.com/ubuntu/ karmic-backports main restricted universe multiverse
That's all.
To get apt-get
working again, change your software sources to the old release repositories.
gksudo gedit /etc/apt/sources.list
delete whatever is in there, and paste the following:
# Required
deb http://old-releases.ubuntu.com/ubuntu/ karmic main restricted universe multiverse
deb http://old-releases.ubuntu.com/ubuntu/ karmic-updates main restricted universe multiverse
deb http://old-releases.ubuntu.com/ubuntu/ karmic-security main restricted universe multiverse
# Optional
#deb http://old-releases.ubuntu.com/ubuntu/ karmic-backports main restricted universe multiverse
That's all.
answered Apr 13 '12 at 9:48
mikewhatevermikewhatever
26.2k8 gold badges75 silver badges88 bronze badges
26.2k8 gold badges75 silver badges88 bronze badges
Thanks mikewhatever, but the result is the same when I try "apt-get install lm-sensors". Maybe there's another missing source: "Reading package lists... Done Building dependency tree Reading state information... Done Package lm-sensors is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package lm-sensors has no installation candidate"
– Rorro
Apr 13 '12 at 10:55
Here are the debs: old-releases.ubuntu.com/ubuntu/pool/main/l/lm-sensors-3. I trust it, you've reloaded the sources list, right?
– mikewhatever
Apr 13 '12 at 12:08
This answer does not work... Why does it have so many upvotes? Did anybody actually test it?
– Tomáš Zato - Reinstate Monica
Aug 15 '14 at 11:00
I've tested it, but the real question is: Why are you still on Karmic? It's been out of support for years, and you should really move on to a more recent release.
– mikewhatever
Aug 15 '14 at 12:13
add a comment
|
Thanks mikewhatever, but the result is the same when I try "apt-get install lm-sensors". Maybe there's another missing source: "Reading package lists... Done Building dependency tree Reading state information... Done Package lm-sensors is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package lm-sensors has no installation candidate"
– Rorro
Apr 13 '12 at 10:55
Here are the debs: old-releases.ubuntu.com/ubuntu/pool/main/l/lm-sensors-3. I trust it, you've reloaded the sources list, right?
– mikewhatever
Apr 13 '12 at 12:08
This answer does not work... Why does it have so many upvotes? Did anybody actually test it?
– Tomáš Zato - Reinstate Monica
Aug 15 '14 at 11:00
I've tested it, but the real question is: Why are you still on Karmic? It's been out of support for years, and you should really move on to a more recent release.
– mikewhatever
Aug 15 '14 at 12:13
Thanks mikewhatever, but the result is the same when I try "apt-get install lm-sensors". Maybe there's another missing source: "Reading package lists... Done Building dependency tree Reading state information... Done Package lm-sensors is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package lm-sensors has no installation candidate"
– Rorro
Apr 13 '12 at 10:55
Thanks mikewhatever, but the result is the same when I try "apt-get install lm-sensors". Maybe there's another missing source: "Reading package lists... Done Building dependency tree Reading state information... Done Package lm-sensors is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package lm-sensors has no installation candidate"
– Rorro
Apr 13 '12 at 10:55
Here are the debs: old-releases.ubuntu.com/ubuntu/pool/main/l/lm-sensors-3. I trust it, you've reloaded the sources list, right?
– mikewhatever
Apr 13 '12 at 12:08
Here are the debs: old-releases.ubuntu.com/ubuntu/pool/main/l/lm-sensors-3. I trust it, you've reloaded the sources list, right?
– mikewhatever
Apr 13 '12 at 12:08
This answer does not work... Why does it have so many upvotes? Did anybody actually test it?
– Tomáš Zato - Reinstate Monica
Aug 15 '14 at 11:00
This answer does not work... Why does it have so many upvotes? Did anybody actually test it?
– Tomáš Zato - Reinstate Monica
Aug 15 '14 at 11:00
I've tested it, but the real question is: Why are you still on Karmic? It's been out of support for years, and you should really move on to a more recent release.
– mikewhatever
Aug 15 '14 at 12:13
I've tested it, but the real question is: Why are you still on Karmic? It's been out of support for years, and you should really move on to a more recent release.
– mikewhatever
Aug 15 '14 at 12:13
add a comment
|
While fossfreedom's answer does a good job of describing and solving the problem, I've found a variant solution that I think is easier and a little more elegant.
The trick is to add http://old-releases.ubuntu.com/ubuntu/
as a mirror, and then tell Software Sources to switch to that mirror.
To do this, backup and edit /usr/share/python-apt/templates/Ubuntu.mirrors
. Choose a fake location for the old-releases server (e.g. #LOC:US
), and add the following line under it:
#LOC:US
http://old-releases.ubuntu.com/ubuntu/
Now open the system's Software Sources dialog, and manually select old-releases.ubuntu.com
as though it were your regional mirror. You should find it listed under the fake location you chose in the previous step.
The next time you reload your package information via Synaptic or Update Manager, you should see it successfully retrieving updated package information.
Works fine, very easy & quick
– doug
Jul 22 '14 at 1:42
add a comment
|
While fossfreedom's answer does a good job of describing and solving the problem, I've found a variant solution that I think is easier and a little more elegant.
The trick is to add http://old-releases.ubuntu.com/ubuntu/
as a mirror, and then tell Software Sources to switch to that mirror.
To do this, backup and edit /usr/share/python-apt/templates/Ubuntu.mirrors
. Choose a fake location for the old-releases server (e.g. #LOC:US
), and add the following line under it:
#LOC:US
http://old-releases.ubuntu.com/ubuntu/
Now open the system's Software Sources dialog, and manually select old-releases.ubuntu.com
as though it were your regional mirror. You should find it listed under the fake location you chose in the previous step.
The next time you reload your package information via Synaptic or Update Manager, you should see it successfully retrieving updated package information.
Works fine, very easy & quick
– doug
Jul 22 '14 at 1:42
add a comment
|
While fossfreedom's answer does a good job of describing and solving the problem, I've found a variant solution that I think is easier and a little more elegant.
The trick is to add http://old-releases.ubuntu.com/ubuntu/
as a mirror, and then tell Software Sources to switch to that mirror.
To do this, backup and edit /usr/share/python-apt/templates/Ubuntu.mirrors
. Choose a fake location for the old-releases server (e.g. #LOC:US
), and add the following line under it:
#LOC:US
http://old-releases.ubuntu.com/ubuntu/
Now open the system's Software Sources dialog, and manually select old-releases.ubuntu.com
as though it were your regional mirror. You should find it listed under the fake location you chose in the previous step.
The next time you reload your package information via Synaptic or Update Manager, you should see it successfully retrieving updated package information.
While fossfreedom's answer does a good job of describing and solving the problem, I've found a variant solution that I think is easier and a little more elegant.
The trick is to add http://old-releases.ubuntu.com/ubuntu/
as a mirror, and then tell Software Sources to switch to that mirror.
To do this, backup and edit /usr/share/python-apt/templates/Ubuntu.mirrors
. Choose a fake location for the old-releases server (e.g. #LOC:US
), and add the following line under it:
#LOC:US
http://old-releases.ubuntu.com/ubuntu/
Now open the system's Software Sources dialog, and manually select old-releases.ubuntu.com
as though it were your regional mirror. You should find it listed under the fake location you chose in the previous step.
The next time you reload your package information via Synaptic or Update Manager, you should see it successfully retrieving updated package information.
edited Feb 23 '18 at 3:14
answered Jun 19 '14 at 2:19
Stuart CookStuart Cook
2312 silver badges4 bronze badges
2312 silver badges4 bronze badges
Works fine, very easy & quick
– doug
Jul 22 '14 at 1:42
add a comment
|
Works fine, very easy & quick
– doug
Jul 22 '14 at 1:42
Works fine, very easy & quick
– doug
Jul 22 '14 at 1:42
Works fine, very easy & quick
– doug
Jul 22 '14 at 1:42
add a comment
|
It appears the Karmic repositories are no longer available.
Since they are for a previous version of Ubuntu, you might consider removing them from your sources list. Take a look at this help page for step-by-step.
add a comment
|
It appears the Karmic repositories are no longer available.
Since they are for a previous version of Ubuntu, you might consider removing them from your sources list. Take a look at this help page for step-by-step.
add a comment
|
It appears the Karmic repositories are no longer available.
Since they are for a previous version of Ubuntu, you might consider removing them from your sources list. Take a look at this help page for step-by-step.
It appears the Karmic repositories are no longer available.
Since they are for a previous version of Ubuntu, you might consider removing them from your sources list. Take a look at this help page for step-by-step.
edited Jan 1 '13 at 0:14
Alvar
15.1k27 gold badges82 silver badges128 bronze badges
15.1k27 gold badges82 silver badges128 bronze badges
answered Dec 31 '12 at 22:49
tekNorahtekNorah
1901 silver badge5 bronze badges
1901 silver badge5 bronze badges
add a comment
|
add a comment
|
You can find the repositories under the "old-releases" server http://old-releases.ubuntu.com/ubuntu/dists/
And about how to edit the /etc/apt/sources.list
https://help.ubuntu.com/community/EOLUpgrades
Thanks gajdipajti, I'm looking for it inside the package list, but cannot find the correct ".deb". My ubuntu already has "libsensors3", but all the packages ask me for the "libsensors4". I know the normal solution should be upgrade, but I cannot do it because the computer is dedicated to be used with a software that only runs on 9.10.
– Rorro
Apr 13 '12 at 10:34
@Rorro: Which software only runs on Ubuntu 9.10?
– unforgettableid
Oct 9 '13 at 1:45
add a comment
|
You can find the repositories under the "old-releases" server http://old-releases.ubuntu.com/ubuntu/dists/
And about how to edit the /etc/apt/sources.list
https://help.ubuntu.com/community/EOLUpgrades
Thanks gajdipajti, I'm looking for it inside the package list, but cannot find the correct ".deb". My ubuntu already has "libsensors3", but all the packages ask me for the "libsensors4". I know the normal solution should be upgrade, but I cannot do it because the computer is dedicated to be used with a software that only runs on 9.10.
– Rorro
Apr 13 '12 at 10:34
@Rorro: Which software only runs on Ubuntu 9.10?
– unforgettableid
Oct 9 '13 at 1:45
add a comment
|
You can find the repositories under the "old-releases" server http://old-releases.ubuntu.com/ubuntu/dists/
And about how to edit the /etc/apt/sources.list
https://help.ubuntu.com/community/EOLUpgrades
You can find the repositories under the "old-releases" server http://old-releases.ubuntu.com/ubuntu/dists/
And about how to edit the /etc/apt/sources.list
https://help.ubuntu.com/community/EOLUpgrades
answered Apr 13 '12 at 9:45
gajdipajtigajdipajti
3,19119 silver badges31 bronze badges
3,19119 silver badges31 bronze badges
Thanks gajdipajti, I'm looking for it inside the package list, but cannot find the correct ".deb". My ubuntu already has "libsensors3", but all the packages ask me for the "libsensors4". I know the normal solution should be upgrade, but I cannot do it because the computer is dedicated to be used with a software that only runs on 9.10.
– Rorro
Apr 13 '12 at 10:34
@Rorro: Which software only runs on Ubuntu 9.10?
– unforgettableid
Oct 9 '13 at 1:45
add a comment
|
Thanks gajdipajti, I'm looking for it inside the package list, but cannot find the correct ".deb". My ubuntu already has "libsensors3", but all the packages ask me for the "libsensors4". I know the normal solution should be upgrade, but I cannot do it because the computer is dedicated to be used with a software that only runs on 9.10.
– Rorro
Apr 13 '12 at 10:34
@Rorro: Which software only runs on Ubuntu 9.10?
– unforgettableid
Oct 9 '13 at 1:45
Thanks gajdipajti, I'm looking for it inside the package list, but cannot find the correct ".deb". My ubuntu already has "libsensors3", but all the packages ask me for the "libsensors4". I know the normal solution should be upgrade, but I cannot do it because the computer is dedicated to be used with a software that only runs on 9.10.
– Rorro
Apr 13 '12 at 10:34
Thanks gajdipajti, I'm looking for it inside the package list, but cannot find the correct ".deb". My ubuntu already has "libsensors3", but all the packages ask me for the "libsensors4". I know the normal solution should be upgrade, but I cannot do it because the computer is dedicated to be used with a software that only runs on 9.10.
– Rorro
Apr 13 '12 at 10:34
@Rorro: Which software only runs on Ubuntu 9.10?
– unforgettableid
Oct 9 '13 at 1:45
@Rorro: Which software only runs on Ubuntu 9.10?
– unforgettableid
Oct 9 '13 at 1:45
add a comment
|
There is an edge case - apt-get claims 16.04 LTS does not exist - where the old package (Vivid, in my case) was not in on the "old-releases" server. But apt-get could only find kernel and Google updates.
I am not sure exactly what my problem was because I had blindly followed the accepted answers sed
command (never a smart move).
This did not work because Vivid was not in the "old-releases" archive but was still on the gb.archive.ubuntu.com
mirror.
In that specific case, the solution was as follows:
sudo -i
edit /etc/apt/sources.list
Carefully go through all the sources and discover one of them was old and wrong and had failed to be properly updated (or something). Or, as I did, search replace from old-releases.ubuntu.com
to gb.archive.ubuntu.com
. It then upgraded, without a problem, to the next release while I caught up on some reading.
So either:
- There was a fault in my sources
- The
gb.archive.unbuntu.com
mirror has an older set of releases.
The takeaway here is that while the majority of answers here may apply in some cases it would pay to be sure that your /etc/apt/sources.list
is correct before you nuke it for the "old-releases" archive.
You can figure out which of the archive or your mirror has the version you need by simply pointing a browser tab at the archive and question and looking for your version name in the folder list. Whichever one has your version, is the source you need to use.
add a comment
|
There is an edge case - apt-get claims 16.04 LTS does not exist - where the old package (Vivid, in my case) was not in on the "old-releases" server. But apt-get could only find kernel and Google updates.
I am not sure exactly what my problem was because I had blindly followed the accepted answers sed
command (never a smart move).
This did not work because Vivid was not in the "old-releases" archive but was still on the gb.archive.ubuntu.com
mirror.
In that specific case, the solution was as follows:
sudo -i
edit /etc/apt/sources.list
Carefully go through all the sources and discover one of them was old and wrong and had failed to be properly updated (or something). Or, as I did, search replace from old-releases.ubuntu.com
to gb.archive.ubuntu.com
. It then upgraded, without a problem, to the next release while I caught up on some reading.
So either:
- There was a fault in my sources
- The
gb.archive.unbuntu.com
mirror has an older set of releases.
The takeaway here is that while the majority of answers here may apply in some cases it would pay to be sure that your /etc/apt/sources.list
is correct before you nuke it for the "old-releases" archive.
You can figure out which of the archive or your mirror has the version you need by simply pointing a browser tab at the archive and question and looking for your version name in the folder list. Whichever one has your version, is the source you need to use.
add a comment
|
There is an edge case - apt-get claims 16.04 LTS does not exist - where the old package (Vivid, in my case) was not in on the "old-releases" server. But apt-get could only find kernel and Google updates.
I am not sure exactly what my problem was because I had blindly followed the accepted answers sed
command (never a smart move).
This did not work because Vivid was not in the "old-releases" archive but was still on the gb.archive.ubuntu.com
mirror.
In that specific case, the solution was as follows:
sudo -i
edit /etc/apt/sources.list
Carefully go through all the sources and discover one of them was old and wrong and had failed to be properly updated (or something). Or, as I did, search replace from old-releases.ubuntu.com
to gb.archive.ubuntu.com
. It then upgraded, without a problem, to the next release while I caught up on some reading.
So either:
- There was a fault in my sources
- The
gb.archive.unbuntu.com
mirror has an older set of releases.
The takeaway here is that while the majority of answers here may apply in some cases it would pay to be sure that your /etc/apt/sources.list
is correct before you nuke it for the "old-releases" archive.
You can figure out which of the archive or your mirror has the version you need by simply pointing a browser tab at the archive and question and looking for your version name in the folder list. Whichever one has your version, is the source you need to use.
There is an edge case - apt-get claims 16.04 LTS does not exist - where the old package (Vivid, in my case) was not in on the "old-releases" server. But apt-get could only find kernel and Google updates.
I am not sure exactly what my problem was because I had blindly followed the accepted answers sed
command (never a smart move).
This did not work because Vivid was not in the "old-releases" archive but was still on the gb.archive.ubuntu.com
mirror.
In that specific case, the solution was as follows:
sudo -i
edit /etc/apt/sources.list
Carefully go through all the sources and discover one of them was old and wrong and had failed to be properly updated (or something). Or, as I did, search replace from old-releases.ubuntu.com
to gb.archive.ubuntu.com
. It then upgraded, without a problem, to the next release while I caught up on some reading.
So either:
- There was a fault in my sources
- The
gb.archive.unbuntu.com
mirror has an older set of releases.
The takeaway here is that while the majority of answers here may apply in some cases it would pay to be sure that your /etc/apt/sources.list
is correct before you nuke it for the "old-releases" archive.
You can figure out which of the archive or your mirror has the version you need by simply pointing a browser tab at the archive and question and looking for your version name in the folder list. Whichever one has your version, is the source you need to use.
answered Jun 5 '17 at 15:12
Matthew Brown aka Lord MattMatthew Brown aka Lord Matt
7663 gold badges12 silver badges27 bronze badges
7663 gold badges12 silver badges27 bronze badges
add a comment
|
add a comment
|
Highly active question. Earn 10 reputation in order to answer this question. The reputation requirement helps protect this question from spam and non-answer activity.
Highly active question. Earn 10 reputation in order to answer this question. The reputation requirement helps protect this question from spam and non-answer activity.
Highly active question. Earn 10 reputation in order to answer this question. The reputation requirement helps protect this question from spam and non-answer activity.
Highly active question. Earn 10 reputation in order to answer this question. The reputation requirement helps protect this question from spam and non-answer activity.
2
It might be worth editing some (or all) answers to this question, as during the weekend after spending quite a while trying to make this work I have by luck realized that they have moved over from
http://old-releases.ubuntu.com/ubuntu/
tohttp://us.archive.ubuntu.com/ubuntu/
(or your own respective two letter abbreviated county code at the beginning) starting from 17.10 (essentially in sync with going back to the beginning of the alphabet).– Isti115
May 6 at 22:22