Friday, 1 February 2013

How-to: Do Release Upgrade


Nut and Bolt by George Hodan Now this sounds really simple. It should be. You log on to your Ubuntu server or desktop and you get a message:

New release 'oneiric' available.
Run 'do-release-upgrade' to upgrade to it.

So you run that:
ubuntu-server11-10:~$ do-release-upgrade

You could do this any time, if you know there's a new release you want to move up to. Here's where things go squonk (you know what that means).

Checking for a new ubuntu release
No new release found

Why does it say there is an upgrade then not find it?


So you try the usual:
sudo apt-get update

Which works and proves your connection to the repositories works and all your keys are valid.


So you try:
sudo apt-get upgrade

Which does nothing since the system thinks it already updated. And the do-release-upgrade message comes back.

It has to be permissions, right? So you try:
sudo do-release-upgrade 

No upgrade found

What the ...?

It seems the answer is in an update key (flag) somewhere I haven't worked out. Life. Too short.

Checking the command switches, I discovered:
do-release-upgrade -d

does the trick. It overrides the messed up keys and gets on with the upgrade. Don't assume if there's a terminal message, that the system recognises an update is available.

Oddly when I trashed my server image and re-installed, the message came up and do-release-upgrade worked off the bat. Which means we have two problems:
  1. Ubuntu can cross-thread it's keys the same as any other operating system (even though we don't have a Registry to trash, it's in a bunch of .cfg files instead).
  2. Joe User needs to be really alert to fix these problems at the command line!
The Prosecution rests, Your Honour. RC

Image credit: Bolt And Nut by George Hodan

No comments:

Post a Comment

At least try to be nice, it won't kill you...