PDA

View Full Version : [ubuntu] Upgrade Karmic Koala server



Alex1200GS
November 23rd, 2011, 11:30 AM
Hi all,

I have a server running Karmic Koala and just decided to upgrade it to the current version, only to find out that the karmic repositories are no longer there.

How should I edit /etc/apt/sources.list so that the OS will realize there are updates available?

Thanks for any hints.

surfer
November 23rd, 2011, 11:44 AM
the repositories for the 'retired' versions are here:

http://old-releases.ubuntu.com/

Alex1200GS
November 23rd, 2011, 10:33 PM
Thanks Surfer!

I updated sources.list with the "retired" repositories, then ran apt-get update/upgrade, even dist-upgrade but to no avail; the OS didn't notice that there's a new version available. Any hint on how to force upgrade?

Alex1200GS
November 25th, 2011, 01:41 AM
So, the answer to my question was "sudo do-release-upgrade", but I need to physically be there as the OS discourages me from upgrading through SSH.

surfer
November 25th, 2011, 04:57 PM
true, it is discouraged. but i've tried it (with a newer release than karmic though) and it worked perfectly. if there is a glitch during the update, you may not be able to reconnect to the ssh server...

good luck if you try!

MAFoElffen
November 25th, 2011, 09:19 PM
So, the answer to my question was "sudo do-release-upgrade", but I need to physically be there as the OS discourages me from upgrading through SSH.Since you updated your sources.list to the EOL repo's already, make sure you have all patches and upgrades up-to-date before going on:


sudo aptitude update && sudo aptitude dist-upgrade
Update your sources.list from Karmic to Lynx:


sudo sed -i 's/karmic/lucid/g' /etc/apt/sources.list && sed -i 's/old-releases/us.archive/g' /etc/apt/sources.list && sudo aptitude update && sudo aptitude dist-upgrade
Then try your release upgrade:


sudo aptitude install update-manager-core && sudo do-release-upgrade
That installs the new update manager before doing a release upgrade.

- If you who get “no release found”, edit the /etc/update-manager/release-upgrades
and if you see “Prompt=lts” change it back to “Prompt=normal”, unless you want to just upgrade to an LTS.

If you get this “no release found” and you have “Prompt=lts” in /etc/update-manager/release-upgrades and don't want to change that release setting because of say unattended updates. Then all you need to do is run




sudo do-release-upgrade –proposed

- The above should work okay over ssh. Has worked Okay for me, but you know there are no 100% guarantees... Things do happen.


Notes on other/alternate methods:
- I do the above method for older installs to newer -and- to get a new install to a development version for testing.

Notes:
Some on old versions may have to do an incremental distribution upgrade to 10.04 first, before going higher. I know 2 ways to do incrementals on old Server Editions...

The first way is to take an Alternate Install CD of the target version. Don't boot off it, but rather plug it in and run ./cdromupgrade from /media/cdrom.

There's another undocumented utility on the Server Edition Install CD that I've used that allows Incremental upgrades on Server. If you booted on a Server Install CD and select Install. it Probes the installed system... If it sees an earlier version of Server, it asks if you want to upgrade that system...