Bizarrely, you can’t update from Intrepid to Jaunty with a simple apt-get dist-upgrade.
I don’t understand why, but you can’t–you simply get the report that no updates are available:
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
What you need to do instead is install the update tool, which is, as far as I can tell, in essence a bash script which does the exact same thing as the apt version above.
The Ubuntu upgrade page describe how to do this:
Install update-manager-core if it is not already installed:sudo apt-get install update-manager-core
Launch the upgrade tool: sudo do-release-upgrade
That’ll download the packages, extract them, and update the system.
I recommend using screen if you’re going to do this remotely: ssh in, hit screen to start a new instance of screen, then run the update script from there. That way you can get out of the instance if you need to (Ctrl+a, then d, to disconnect). Bizarrely, the instance will run in the background even if you end the screen instance–I had problems reconnecting to the session from a different computer, something about a tunnel remaining open till the process closed, but could reconnect via screen -R at the original (albeit remote) computer.
Upgrading to Jaunty Via the Command Line
Bizarrely, you can’t update from Intrepid to Jaunty with a simple
apt-get dist-upgrade.I don’t understand why, but you can’t–you simply get the report that no updates are available:
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.What you need to do instead is install the update tool, which is, as far as I can tell, in essence a bash script which does the exact same thing as the apt version above.
The Ubuntu upgrade page describe how to do this:
Install update-manager-core if it is not already installed:
sudo apt-get install update-manager-coreLaunch the upgrade tool:
sudo do-release-upgradeThat’ll download the packages, extract them, and update the system.
I recommend using screen if you’re going to do this remotely: ssh in, hit
screento start a new instance of screen, then run the update script from there. That way you can get out of the instance if you need to (Ctrl+a, then d, to disconnect). Bizarrely, the instance will run in the background even if you end the screen instance–I had problems reconnecting to the session from a different computer, something about a tunnel remaining open till the process closed, but could reconnect viascreen -Rat the original (albeit remote) computer.