Upgrade 8.10 intrepid to 9.04 jaunty with update manager fails

[walter23]

I know its a been over a year now but I was wondering if you ever got around this problem? I have several servers that are having the same problem. I'm stuck on 8.10, the initially installed OS, but I want to upgrade to 10.04. Any help would be great. Thanks.

I just encountered this problem myself and I think I found the solution (upgrading as I write here; no guarantee it will finish, will update later). You can download the distribution upgrade tarball, untar it, and run an upgrade command manually. I'm going 8.10 to 9.04 (and then trying to move on after that).

I did all the steps described here: https://help.ubuntu.com/community/EOLUpgrades

And then here: https://help.ubuntu.com/community/EOLUpgrades/Intrepid

And got stuck at "do-release-upgrade" with the same errors:

Failed Upgrade tool signature
Failed Upgrade tool

What I found was this:

http://ubuntuforums.org/showthread.php?t=1159312

Where a manual upgrade is described.

Basically you run these commands from some temporary directory.

wget http://old-releases.ubuntu.com/ubuntu/dists/jaunty/main/dist-upgrader-all/current/jaunty.tar.gz

tar xzvf jaunty.tar.gz
gksu "./dist-upgrade.py --frontend=DistUpgradeViewGtk"

And that'll get you going with the gtk interface. I'm writing this as it downloads the upgrade packages so I don't know for sure that it will complete yet, but it looks like it's working fine. I wasn't getting anywhere with update-manager or the command line version.

Notice I left out the gpg signature check. That's because it fails. This may be a security issue; I'm not sure. It seems likely it's the cause of the problem we're experiencing with the automatic upgrade though.

I did find this thread that suggests adding a trusted key:

http://ubuntuforums.org/showthread.php?t=285904

Maybe that will "fix it" so you can just run the update normally.

And this: http://www.google.ca/search?hl=en&so...&aqi=&aql=&oq=

Another suggestion is to just delete your gpg keys and reinstall them: http://techpad.co.uk/content.php?sid=84

[Hedgehog1]

I just encountered this problem myself and I think I found the solution (upgrading as I write here; no guarantee it will finish, will update later). ...

I can see doing this and enjoying the technical challenge of it all.

But this amount of work is orders of magnitude more effort than a clean install or a separate '/' and '/home' install.

Is there a benefit I am missing?

Just wondering...

The Hedge

[walter23]

Is there a benefit I am missing?

I'm using relatively old hardware, I can't find my USB stick, and I don't have any blank CDs. Maybe that's not the best reason to go this route, but it is what it is.

[Hedgehog1]

I'm using relatively old hardware, I can't find my USB stick, and I don't have any blank CDs. Maybe that's not the best reason to go this route, but it is what it is.

Works for me - you are using available materials; gotcha!

[mariuxx]

Hi guys...

Sorry to disturb the harmony here, but i have a server on a remote site that should have been upgraded ages ago...or a year at least.

Obviously the GTK trick won't work for me.

It's now running 8.10 Intrepid, which i understand must (or should) be upgraded to 9.04 Jaunty

I included the old-releases lines in sources.list

deb http://old-releases.ubuntu.com/ubuntu/ intrepid main restricted universe multiverse
deb http://old-releases.ubuntu.com/ubuntu/ intrepid-updates main restricted universe multiverse
deb http://old-releases.ubuntu.com/ubuntu/ intrepid-security main restricted universe multiverse

That made it possible to update&upgrade the system.

However, issuing:

sudo do-release-upgrade

still only yields:

Checking for a new ubuntu release
Failed Upgrade tool signature
Failed Upgrade tool
Done downloading
extracting 'jaunty.tar.gz'
Failed to extract
Extracting the upgrade failed. There may be a problem with the network or with the server.

I seems the signature for the upgrade tool cannot be verified (or something like that), I have also used:

apt-get install ubuntu-keyring

which works ok, the keyring is installed, but still the same error...

Anyone?

[aerotux]

Hi guys...

Sorry to disturb the harmony here, but i have a server on a remote site that should have been upgraded ages ago...or a year at least.

Obviously the GTK trick won't work for me.

It's now running 8.10 Intrepid, which i understand must (or should) be upgraded to 9.04 Jaunty

I included the old-releases lines in sources.list

deb http://old-releases.ubuntu.com/ubuntu/ intrepid main restricted universe multiverse
deb http://old-releases.ubuntu.com/ubuntu/ intrepid-updates main restricted universe multiverse
deb http://old-releases.ubuntu.com/ubuntu/ intrepid-security main restricted universe multiverse

That made it possible to update&upgrade the system.

However, issuing:

sudo do-release-upgrade

still only yields:

Checking for a new ubuntu release
Failed Upgrade tool signature
Failed Upgrade tool
Done downloading
extracting 'jaunty.tar.gz'
Failed to extract
Extracting the upgrade failed. There may be a problem with the network or with the server.

I seems the signature for the upgrade tool cannot be verified (or something like that), I have also used:

apt-get install ubuntu-keyring

which works ok, the keyring is installed, but still the same error...

Anyone?

Walter23 (post #11) worked for me, I was having the same issues as you.

[PierceNicholas]

I'm also stuck on 8.10 but after playing around a little I know have the look of 9.04, yet my lbs_release -r states I'm on 8.10 still.

Using Kubuntu and a returning linux user but I've forgotten most of it.

Also as much as it would be tons and millions and even lightyears better, faster, stronger to do a fresh install, I can't do that. I simply _need_ this to work via upgrade methods.

Does anyone have anything that will work?

[MountainX]

try this:
http://serverfault.com/questions/278...epid-to-jaunty

I'm in the process of using these steps from the link above:

I think the problem can be solved in a much simpler fashion without having to use another machine. Here is what I did:
Copied the old (incorrect) file from http://changelogs.ubuntu.com/meta-release to a local file (say) /etc/meta-release.rvg I modified /etc/meta-release.rvg so that "archive" was replaced by "old-releases"
Modified /etc/update-manager/meta-release so that it pointed to my local file rather than the incorrect URI on the ubuntu site - here is what it looked like after my change:
[METARELEASE]
URI = file:///etc/meta-release.rvg
URI_LTS = http://changelogs.ubuntu.com/meta-release-lts
URI_UNSTABLE_POSTFIX = -development
URI_PROPOSED_POSTFIX = -proposed
I then ran do-release-upgrade and everything worked like a charm
Regards,
Rajendra Gokhale

It got me past this error:

root@server1:/# do-release-upgrade
Checking for a new ubuntu release
Failed Upgrade tool signature
Failed Upgrade tool
Done downloading
extracting 'jaunty.tar.gz'
Failed to extract
Extracting the upgrade failed. There may be a problem with the network or with the server.

The next challenge will be to complete the upgrade from Jaunty to Karmic... (and yes, I also have good reasons for doing the stepwise upgrades rather than a fresh install).

In the future, I'll keep my servers on LTS releases only. ;)