Ubuntu: Problem upgrading from Jaunty to Karmic

Ubuntuubuntu-9.04ubuntu-9.10

When i try to upgrade from jaunty to karmic i get this problem:

root@server:~# sudo do-release-upgrade
Checking for a new ubuntu release
Done Upgrade tool signature
Done Upgrade tool
Done downloading
extracting 'lucid.tar.gz'
authenticate 'lucid.tar.gz' against 'lucid.tar.gz.gpg'
tar: Removing leading `/' from member names

Reading cache

Checking package manager

Can not upgrade

An upgrade from 'jaunty' to 'lucid' is not supported with this tool.

I have no idea why it tries to upgrade to lucid when i need to upgrade to karmic first. I guess it gets the word "lucid" from somewhere but i have no idea where to start looking.

Best Answer

Solved it. Turns out that /etc/update-manager/meta-release is pointing to http://changelogs.ubuntu.com/meta-release and that file says:

Dist: karmic
Name: Karmic Koala
Version: 9.10
Date: Thu, 29 Oct 2009 12:00:00 UTC
Supported: 0
Description: This is the 9.10 release
Release-File: http://archive.ubuntu.com/ubuntu/dists/karmic/Release
ReleaseNotes: http://changelogs.ubuntu.com/EOLReleaseAnnouncement
UpgradeTool: http://archive.ubuntu.com/ubuntu/dists/karmic-proposed/main/dist-upgrader-all/0.126.9/karmic.tar.gz
UpgradeToolSignature: http://archive.ubuntu.com/ubuntu/dists/karmic-proposed/main/dist-upgrader-all/0.126.9/karmic.tar.gz.gpg

I downloaded the file, changed "Supported: 0" to "Supported: 1" and hosted the file on my own webserver and pointed the meta-release to my server instead. Worked perfectly.

Don't know if there is a reason Ubuntu wants to make it impossible to do this upgrade or if accidentally changed supported to 0.

Related Solutions

Ubuntu – Grub Error 2 in Ubuntu Jaunty Server

Figured this out, but it wasn't pretty. I'd install from the server cd, and on reboot it would fail right off the bat, saying only 'grub error 2' (changed eventually to 22). Repairing grub from the install cd didn't fix the problem.

First, it turns out that the order of the sata controllers got switched around on the new install. All the disks were wiped but the hardware wasn't shuffled around, so I'm not sure why this would happen. The problem with this is that only one of the sata cards (the one previously controlling sda-sdc, now sdd-sdf) is bootable. Having figured this out I installed to sdd, but prior installation attempts on the non-bootable disks were visible by grub once it loaded, and deleting them left it loading grub from sdd and looking for a non-existent root on sda-sdc. The solution was to wipe everything again, install to sdd, and run a terminal from the live cd:

sudo grub
grub> find /boot/grub/stage1
 (hd3,0)
grub> root (hd3,0)
grub> setup (hd3)
grub> quit

Makes sense since in /boot/grub/device.map hd3 is mapped to /dev/sdd.

I couldn't find a way in the bios to give the bootable controller any kind of priority for the device ordering, and rearranging the HD boot order in bios didn't seem to matter. Last resort would be to open it up and switch the pci slots of the controller cards around, but since it boots fine now I'm not going to try this -- maybe next upgrade.

Ubuntu – jetty 6.x on ubuntu jaunty 9.04

jetty is currently just support by debian sid. Debian sid is the unstable branch, which will become the new stable on the next release. You could try to backport the package to your current system but this is not a trivial task.
You can use dpk -i pkgname to install a single debian package. Missing dependencies are not automatically installed, so this is not exactly what apt-get would do.

The easiest way to install jetty would be to download the binary package, extract it and start the included startscript. If you want it to be started on reboot you could write a init-script to do that.

Best Answer

Related Solutions

Ubuntu – Grub Error 2 in Ubuntu Jaunty Server

Ubuntu – jetty 6.x on ubuntu jaunty 9.04

Related Topic