个人工具

“UbuntuHelp:EOLUpgrades”的版本间的差异

来自Ubuntu中文

跳转至: 导航, 搜索
(创建新页面为 '{{From|https://help.ubuntu.com/community/EOLUpgrades}} {{Languages|UbuntuHelp:EOLUpgrades}} == Introduction == This upgrade guide will explain how to upgrade an EOL release of U...')
 
 
(未显示同一用户的1个中间版本)
第1行: 第1行:
 
{{From|https://help.ubuntu.com/community/EOLUpgrades}}
 
{{From|https://help.ubuntu.com/community/EOLUpgrades}}
 
{{Languages|UbuntuHelp:EOLUpgrades}}
 
{{Languages|UbuntuHelp:EOLUpgrades}}
 +
#title Upgrading End of Life releases
 
== Introduction ==
 
== Introduction ==
This upgrade guide will explain how to upgrade an EOL release of Ubuntu to another EOL release of Ubuntu and then get to a supported system. This is meant for systems which cannot install a newer version of update-manager as described in bug 264181 (for link see the See also section).
+
This page will explain how to upgrade an [http://en.wikipedia.org/wiki/End-of-life_(product) End of Life (EOL)] release of Ubuntu to a supported system. This guide is not limited to Ubuntu (with the Gnome desktop),  any Ubuntu flavor (Kubuntu/Edubuntu and/or server installation and others) can use this guide.
If you want to know what EOL means, have a look overhere: [http://en.wikipedia.org/wiki/End-of-life_(product)]
+
For upgrading supported releases please refer to [[UbuntuHelp:Upgrades| this document]]. Mac users may have some difficulty upgrading to the most current release around versions 7.04/7.10.
This upgrade exercise has been executed on a fresh install of Ubuntu 6.10 and we will upgrade to 8.04.2 LTS. All the repositories which are on a default installation are enabled, this is the sources.list file which we used to start the upgrade process, all comments have been removed to make it a shorter list.
+
If you want to know whether your release is EOL please have a look at the following resources:
 +
* https://wiki.ubuntu.com/Releases
 +
* http://en.wikipedia.org/wiki/List_of_Ubuntu_releases
 +
* http://www.ubuntu.com/products/ubuntu/release-cycle
 +
These guides assumes that the user knows his way on the terminal, as no graphical tools are used. This said, the steps for executing all the commands are actually copy/paste-able so everyone, from beginner to advanced user running EOL releases of Ubuntu can execute the upgrade(s).
 +
In case of problems you should be aware that most (if not all) of the releases which are mentioned in this guide are UNSUPPORTED, and getting help may be a bit tricky since most of us have already upgraded to a more recent version of Ubuntu. You could always try to run the upgrade path first in a virtual machine (vmware/virtualbox/qemu or others). All the upgrades of this guide were performed and tested in virtual machines (except for 6.10 to 7.10 which were executed on a Compaq/HP laptop NC6000). You can make a backup of your disks/partitions using [http://www.clonezilla.org  clonezilla].
 +
=== Why upgrade ===
 +
Why should you upgrade in stead of performing a clean install of a supported version? Some don't like to perform new installations when there is a possibility to upgrade. The advantage of this is that you can keep your current configuration without having to change much. This is often the case in production environments where you don't want to lose a machine just because it needs a higher OS version.
 +
The scientific approach. It is possible to do, so why wouldn't we give it a shot?
 +
This is how I started out writing this guide. I had to help someone else, who was in another timezone and I thought my sleep was precious so I wrote a guide telling him how to upgrade to 8.04. When I was finished I decided it was fun to see if I could upgrade from 4.10 to the most current version (I admit, I took a shortcut when I arrived at 6.06, I upgraded directly to 8.04).
 +
The last reason is more a flame, why would we do it the Microsoft way? If we don't know, just restart... Why don't we try to fix the issue, even if it takes a bit more time. The time it takes per upgrade is dependent on your installation.
 +
There are reasons why one should not upgrade, but rather reinstall.
 +
From 9.04 (jaunty) ext4 becomes available. If you want to benefit from the new features ext4 has you then you might just as well reinstall one of the supported releases (LTS and non-LTS).
 +
== Upgrade ==
 +
This guide consists out of four main parts.
 +
The first part will cover upgrading from 8.10 to 9.04 and up (eventually to 10.04). We will do the following upgrades, 8.10 to 9.04 to 9.10 to 10.04 LTS.
 +
The second part will cover upgrading from 6.10 to 8.04.3 LTS. We will do the following upgrades, 6.10 to 7.04 to 7.10 to 8.04.3 LTS.
 +
The third part covers upgrading from 6.06 LTS to 8.04.3 LTS. This is the preferred way of upgrading to 8.04.3 from 6.06. You will not need to upgrade to 7.x. At the time of writing this is not an EOL upgrade.
 +
The fourth part will be about upgrading 4.10 to 6.06.2 LTS. We will do the following upgrades, 4.10 to 5.04 to 5.10 to 6.06.2 LTS.
 +
Note:: Ubuntu 6.06's support has ended in June 2009 for desktops and will end June 2011 for servers. This will mean a lot of desktop applications are not supported/updated anymore. See [http://people.canonical.com/~ubuntu-security//dapper/supported.txt  this list] of supported packages. Upgrading 6.06.x to 8.04 is regarded as a regular upgrade. Please see [[UbuntuHelp:DapperUpgrades|DapperUpgrades]] or [[UbuntuHelp:HardyUpgrades|HardyUpgrades]] for more information.
 +
=== Requirements ===
 +
==== /etc/apt/sources.list ====
 +
Please make sure you have the following sources.list, change CODENAME to your release, e.g. breezy.
 
<pre><nowiki>
 
<pre><nowiki>
deb http://nl.archive.ubuntu.com/ubuntu/ edgy main restricted
+
# Required
deb-src http://nl.archive.ubuntu.com/ubuntu/ edgy main restricted
+
deb http://old-releases.ubuntu.com/ubuntu/ CODENAME main restricted universe multiverse
 +
deb http://old-releases.ubuntu.com/ubuntu/ CODENAME-updates main restricted universe multiverse
 +
deb http://old-releases.ubuntu.com/ubuntu/ CODENAME-security main restricted universe multiverse
  
deb http://nl.archive.ubuntu.com/ubuntu/ edgy-updates main restricted
+
# Optional
deb-src http://nl.archive.ubuntu.com/ubuntu/ edgy-updates main restricted
+
#deb http://old-releases.ubuntu.com/ubuntu/ CODENAME-backports main restricted universe multiverse
 
+
deb http://nl.archive.ubuntu.com/ubuntu/ edgy universe
+
deb-src http://nl.archive.ubuntu.com/ubuntu/ edgy universe
+
 
+
deb http://nl.archive.ubuntu.com/ubuntu/ edgy-backports main restricted universe multiverse
+
deb-src http://nl.archive.ubuntu.com/ubuntu/ edgy-backports main restricted universe multiverse
+
 
+
deb http://security.ubuntu.com/ubuntu edgy-security main restricted
+
deb-src http://security.ubuntu.com/ubuntu edgy-security main restricted
+
deb http://security.ubuntu.com/ubuntu edgy-security universe
+
deb-src http://security.ubuntu.com/ubuntu edgy-security universe
+
 
</nowiki></pre>
 
</nowiki></pre>
This guides assumes that the user knows his way on the terminal, as no graphical tools are used.
+
You can make use of -backports if you want, or -proposed.
== 6.10 to 7.04 ==
+
For more information about repositories https://help.ubuntu.com/community/Repositories/Ubuntu
* Change all the archive.ubuntu.com (or your countries mirror) URL to old-releases.ubuntu.com
+
==== Dependencies ====
 +
You should also make sure some meta-packages are installed so the upgrade can continue without problems:
 +
===== Update-manager =====
 +
From version 6.06 and up you will need to install the [[UbuntuHelp:apt:update-manager-core,update-manager|update-manager and update-manager-core]] packages.
 
<pre><nowiki>
 
<pre><nowiki>
sudo perl -p -i.ORIG -e 's/(?:(?:\w+.)?archive|security).(ubuntu.com)/old-releases.$1/' /etc/apt/sources.list
+
sudo aptitude install update-manager update-manager-core
 
</nowiki></pre>
 
</nowiki></pre>
* Update the package list
+
===== Ubuntu-desktops =====
 +
If you run a particular desktop version, you might want to reinstall this package to resolve any issue with dependencies of that package. You can (re)install these -desktop packages before or after your upgrade.
 +
To find out if you which desktop package you want to (re)install: `dpkg -l | grep tu-desktop`. Or search for one by running `aptitude search tu-desktop`.  The correct commands to (re)install are:
 
<pre><nowiki>
 
<pre><nowiki>
sudo aptitude update
+
# The Kubuntu desktop
</nowiki></pre>
+
sudo aptitude install kubuntu-desktop
* Install update manager
+
# or
<pre><nowiki>
+
sudo aptitude reinstall kubuntu-desktop
sudo aptitude install update-manager-core update-manager
+
</nowiki></pre>
+
* Upgrade all current packages
+
<pre><nowiki>
+
sudo aptitude upgrade
+
</nowiki></pre>
+
* Upgrade your complete system
+
You need to run do-release-upgrade once, it will fail, but that doesn't matter. We will trigger the upgrade process from a different executable once we ran do-release-upgrade.
+
<pre><nowiki>
+
sudo do-release-upgrade
+
</nowiki></pre>
+
You will now see the following messages on your screen, directly after executing the command:
+
<pre><nowiki>
+
wesleys@ubuntu-eol-upgrade:~$ sudo do-release-upgrade
+
Checking for a new ubuntu release
+
Done Upgrade tool signature
+
Done Upgrade tool
+
Done downloading
+
extracting '/tmp/tmpH9WhkH/feisty.tar.gz'
+
authenticate '/tmp/tmpH9WhkH/feisty.tar.gz' against '/tmp/tmpH9WhkH/feisty.tar.gz.gpg'
+
</nowiki></pre>
+
And many more error messages, you can ignore them for now. Remember the directory as seen in the sniplet above. The upgrade process changes old-releases.ubuntu.com links to archive.ubuntu.com, because we upgrade to another EOL release the archive link will not work. To prevent this from happening we are going to patch the upgrade controler script.
+
Contents of the patch file:
+
<pre><nowiki>
+
--- DistUpgradeControler.py.ORIG        2009-01-29 18:51:43.000000000 +0100
+
+++ DistUpgradeControler.py    2009-01-29 18:52:44.000000000 +0100
+
@@ -352,11 +352,11 @@
+
            # them back to archive.ubuntu.com - now this is a problem
+
            # of course for people upgrading from EOL release to a
+
            # EOL release
+
-            if (not entry.disabled and
+
-                entry.uri.startswith("http://old-releases.ubuntu.com/ubuntu")):
+
-                entry.uri = "http://archive.ubuntu.com/ubuntu"
+
-                logging.debug("transitioning old-releases.ubuntu.com to '%s' " % entry)
+
-                continue
+
+            #if (not entry.disabled and
+
+            #    entry.uri.startswith("http://old-releases.ubuntu.com/ubuntu")):
+
+            #    entry.uri = "http://archive.ubuntu.com/ubuntu"
+
+            #    logging.debug("transitioning old-releases.ubuntu.com to '%s' " % entry)
+
+            #    continue
+
 
+
            logging.debug("examining: '%s'" % entry)
+
            # check if it's a mirror (or offical site)
+
</nowiki></pre>
+
* Apply the patch:
+
<pre><nowiki>
+
cd /tmp/tmpH9WhkH/
+
sudo patch < DistUpgradeControler.py.patch
+
# or if you have the patch file in your homedir
+
sudo patch < $HOME/DistUpgradeControler.py.patch
+
</nowiki></pre>
+
NOTE:
+
If you do not have patch installed run the command below, or make these changes manually. You will need root privileges to edit the file (as you can see from the sudo patch line).
+
<pre><nowiki>
+
sudo aptitude install patch
+
</nowiki></pre>
+
When you have applied the patch execute the following command:
+
<pre><nowiki>
+
sudo ./feisty --frontend DistUpgradeViewText --mode=server
+
</nowiki></pre>
+
Now reboot your machine. When your machine comes back up again you are running feisty. You can check this by running
+
<pre><nowiki>
+
lsb_release -a
+
</nowiki></pre>
+
== 7.04 to 7.10 ==
+
This upgrade did not go as smooth as I expected. I expected the upgrade process to be similar to 6.10 -> 7.04 like in bug 264181, but that was not the case.
+
* Run do-release-upgrade
+
<pre><nowiki>
+
sudo do-release-upgrade
+
</nowiki></pre>
+
It will fail, because it does not rewrite old-releases.ubuntu.com to archive.ubuntu.com as expected. But we need to run it once, to get some files from the feisty repo's. Make sure you remember that /tmp directory again, we are going to need it in a sec. If you did not record the location we can find it pretty easy:
+
<pre><nowiki>
+
find /tmp -name gutsy
+
</nowiki></pre>
+
This will tell you where the upgrade script resides and you just need to enter that directory.
+
* Change your sources.list
+
We now need to change our sources.list to have only gutsy (7.10) repositories, you may wish to use a different mirror (archive then becomes in my case nl.archive).
+
<pre><nowiki>
+
sudo perl -p -i.feisty -e 's/old-releases.ubuntu.com/archive.ubuntu.com/g' /etc/apt/sources.list
+
</nowiki></pre>
+
If you have the security repositories make sure you change them to security.ubuntu.com, eg
+
<pre><nowiki>
+
deb http://archive.ubuntu.com/ubuntu feisty-security main restricted
+
# Changes to
+
deb http://security.ubuntu.com/ubuntu feisty-security main restricted
+
</nowiki></pre>
+
Once this is done we are going to change feisty to gutsy:
+
<pre><nowiki>
+
sudo perl -p -i -e 's/feisty/gutsy/g' /etc/apt/sources.list
+
</nowiki></pre>
+
Some users have mailed me that there are some extra steps to complete the upgrade. We need to edit the prerequists-sources.list in the /tmp directory to make sure the release-upgrader-dpkg and release-upgrader-apt packages can be installed.
+
<pre><nowiki>
+
cd /tmp/tmpeBHg_m
+
 
+
perl -p -i.feisty -e 's/(http:\/\/).*archive(.ubuntu.com)/${1}old-releases$2/' prerequists-sources.list
+
</nowiki></pre>
+
Or make the changes manually:
+
<pre><nowiki>
+
deb http://${countrymirror}archive.ubuntu.com/ubuntu feisty-backports main/debian-installer
+
 
+
to
+
 
+
deb http://old-releases.ubuntu.com/ubuntu feisty-backports main/debian-installer
+
 
+
 
</nowiki></pre>
 
</nowiki></pre>
* Continue the upgrade process
+
===== Kernels =====
 +
* 8.04 and up: [[UbuntuHelp:apt:linux-image-generic,linux-headers-generic|apt:linux-image-generic,linux-headers-generic]], [[UbuntuHelp:apt:linux-image-server,linux-headers-server|apt:linux-image-server,linux-headers-server]] or [[UbuntuHelp:apt:linux-image-virtual,linux-headers-virtual|apt:linux-image-virtual,linux-headers-virtual]]
 
<pre><nowiki>
 
<pre><nowiki>
cd /tmp/tmpeBHg_m
+
sudo aptitude install linux-image-generic linux-headers-generic
sudo ./gutsy --frontend DistUpgradeViewText --mode=server
+
# or
 +
sudo aptitude install linux-image-server linux-headers-server
 +
# or
 +
sudo aptitude install linux-image-virtual linux-headers-virtual
 
</nowiki></pre>
 
</nowiki></pre>
Now reboot your machine. When your machine comes back up again you are running gutsy. You can check this by running
+
* 5.04: linux-image-386 and linux-headers-386
 
<pre><nowiki>
 
<pre><nowiki>
lsb_release -a
+
sudo aptitude install linux-image-386 linux-headers-386
 
</nowiki></pre>
 
</nowiki></pre>
== 7.10 to 8.04.2 ==
+
* 4.10: linux-image-386 and linux-kernel-headers
Please have a look at the following documentation: https://help.ubuntu.com/community/HardyUpgrades
+
But in short:
+
 
<pre><nowiki>
 
<pre><nowiki>
sudo do-release-upgrade
+
sudo aptitude install linux-image-386 linux-kernel-headers
 
</nowiki></pre>
 
</nowiki></pre>
Reboot and you are good to go.
+
=== Known issues ===
 +
Some issues are related to apt-get upgrade and dist-upgrade commands. If you get calculation errors when running do-release-upgrade you can resolve this issue by running `do-release-upgrade -m desktop` or you can remove the ubuntu-desktop package. When aptitude is used there is no need for this. Please follow the guide exactly, when this guide wants to use apt-get, it will tell you :)
 +
If you run into individual dependency issues you need to resolve these individually. You can use `sudo apt-get -f install` for this. And then continue by running e.g. `sudo ./feisty --frontend DistUpgradeViewTextm -mode=server`. Replace feisty with the release where you upgrade to, this will continue the do-release-upgrade process.
 +
== 8.10 to 9.04 (Intrepid to Jaunty) ==
 +
This upgrade exercise has been executed on a fresh install of Ubuntu 8.10 and we will upgrade to 9.04.
 +
Intrepid 8.10 to Jaunty 9.04:: [[UbuntuHelp:EOLUpgrades/Intrepid|EOLUpgrades/Intrepid]]
 +
== 6.10 to 8.04 (Edgy to Hardy) ==
 +
This upgrade exercise has been executed on a fresh install of Ubuntu 6.10 and we will upgrade to 8.04.3 LTS.
 +
Edgy 6.10 to Feisty 7.04:: [[UbuntuHelp:EOLUpgrades/Edgy|EOLUpgrades/Edgy]]
 +
Feisty 7.04 to Gutsy 7.10:: [[UbuntuHelp:EOLUpgrades/Feisty|EOLUpgrades/Feisty]]
 +
Gutsy 7.10 to Hardy 8.04:: [[UbuntuHelp:EOLUpgrades/Gutsy|EOLUpgrades/Gutsy]]
 +
== 6.06 to 8.04.3 (Dapper to Hardy) ==
 +
Dapper 6.06 to Hardy 8.04.3:: [[UbuntuHelp:EOLUpgrades/Dapper|EOLUpgrades/Dapper]]
 +
== 4.10 to 6.06 (Warty to Dapper) ==
 +
This upgrade exercise has been executed on a fresh install of Ubuntu 4.10 and we will upgrade to 6.06.2 LTS.
 +
Warty 4.10 to Hoary 5.04:: [[UbuntuHelp:EOLUpgrades/Warty|EOLUpgrades/Warty]]
 +
Hoary 5.04 to Breezy 5.10:: [[UbuntuHelp:EOLUpgrades/Hoary|EOLUpgrades/Hoary]]
 +
Breezy 5.10 to Dapper 6.06.2:: [[UbuntuHelp:EOLUpgrades/Breezy|EOLUpgrades/Breezy]]
 
== See Also ==
 
== See Also ==
 
Upgrade path:
 
Upgrade path:
* https://help.ubuntu.com/community/GutsyUpgrades - Upgrade process from Feisty (7.04) to Gutsy (7.10)
+
* https://help.ubuntu.com/community/HardyUpgrades - Upgrade process from Breezy (6.06) and Gutsy (7.10) to Hardy (8.04)
* https://help.ubuntu.com/community/HardyUpgrades - Upgrade process from Gutsy (7.10) to Hardy (8.04)
+
 
Bugs:
 
Bugs:
 
* https://bugs.launchpad.net/bugs/264181 - Bug where EOL to supported version upgrade fails (FIXED)
 
* https://bugs.launchpad.net/bugs/264181 - Bug where EOL to supported version upgrade fails (FIXED)
 
* https://bugs.launchpad.net/bugs/319324 - I suspect this is a follow up bug on 264181
 
* https://bugs.launchpad.net/bugs/319324 - I suspect this is a follow up bug on 264181
 
== Comments ==
 
== Comments ==
If you think something is incorrect on this page please contact me. My contact details can be found on launchpad: https://launchpad.net/~wesleys
+
If you think something is incorrect on this page please contact me. You can find my contact details [[UbuntuHelp:wesleys|here]].
 +
I would also like to hear from you if this guide didn't help you, the more feedback I get, the better this guide will get.
 
----
 
----
 
[[category:CategoryUpgrade]]
 
[[category:CategoryUpgrade]]
  
 
[[category:UbuntuHelp]]
 
[[category:UbuntuHelp]]

2010年5月19日 (三) 22:16的最新版本

  1. title Upgrading End of Life releases

Introduction

This page will explain how to upgrade an End of Life (EOL) release of Ubuntu to a supported system. This guide is not limited to Ubuntu (with the Gnome desktop), any Ubuntu flavor (Kubuntu/Edubuntu and/or server installation and others) can use this guide. For upgrading supported releases please refer to this document. Mac users may have some difficulty upgrading to the most current release around versions 7.04/7.10. If you want to know whether your release is EOL please have a look at the following resources:

These guides assumes that the user knows his way on the terminal, as no graphical tools are used. This said, the steps for executing all the commands are actually copy/paste-able so everyone, from beginner to advanced user running EOL releases of Ubuntu can execute the upgrade(s). In case of problems you should be aware that most (if not all) of the releases which are mentioned in this guide are UNSUPPORTED, and getting help may be a bit tricky since most of us have already upgraded to a more recent version of Ubuntu. You could always try to run the upgrade path first in a virtual machine (vmware/virtualbox/qemu or others). All the upgrades of this guide were performed and tested in virtual machines (except for 6.10 to 7.10 which were executed on a Compaq/HP laptop NC6000). You can make a backup of your disks/partitions using clonezilla.

Why upgrade

Why should you upgrade in stead of performing a clean install of a supported version? Some don't like to perform new installations when there is a possibility to upgrade. The advantage of this is that you can keep your current configuration without having to change much. This is often the case in production environments where you don't want to lose a machine just because it needs a higher OS version. The scientific approach. It is possible to do, so why wouldn't we give it a shot? This is how I started out writing this guide. I had to help someone else, who was in another timezone and I thought my sleep was precious so I wrote a guide telling him how to upgrade to 8.04. When I was finished I decided it was fun to see if I could upgrade from 4.10 to the most current version (I admit, I took a shortcut when I arrived at 6.06, I upgraded directly to 8.04). The last reason is more a flame, why would we do it the Microsoft way? If we don't know, just restart... Why don't we try to fix the issue, even if it takes a bit more time. The time it takes per upgrade is dependent on your installation. There are reasons why one should not upgrade, but rather reinstall. From 9.04 (jaunty) ext4 becomes available. If you want to benefit from the new features ext4 has you then you might just as well reinstall one of the supported releases (LTS and non-LTS).

Upgrade

This guide consists out of four main parts. The first part will cover upgrading from 8.10 to 9.04 and up (eventually to 10.04). We will do the following upgrades, 8.10 to 9.04 to 9.10 to 10.04 LTS. The second part will cover upgrading from 6.10 to 8.04.3 LTS. We will do the following upgrades, 6.10 to 7.04 to 7.10 to 8.04.3 LTS. The third part covers upgrading from 6.06 LTS to 8.04.3 LTS. This is the preferred way of upgrading to 8.04.3 from 6.06. You will not need to upgrade to 7.x. At the time of writing this is not an EOL upgrade. The fourth part will be about upgrading 4.10 to 6.06.2 LTS. We will do the following upgrades, 4.10 to 5.04 to 5.10 to 6.06.2 LTS. Note:: Ubuntu 6.06's support has ended in June 2009 for desktops and will end June 2011 for servers. This will mean a lot of desktop applications are not supported/updated anymore. See this list of supported packages. Upgrading 6.06.x to 8.04 is regarded as a regular upgrade. Please see DapperUpgrades or HardyUpgrades for more information.

Requirements

/etc/apt/sources.list

Please make sure you have the following sources.list, change CODENAME to your release, e.g. breezy.

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

# Optional
#deb http://old-releases.ubuntu.com/ubuntu/ CODENAME-backports main restricted universe multiverse

You can make use of -backports if you want, or -proposed. For more information about repositories https://help.ubuntu.com/community/Repositories/Ubuntu

Dependencies

You should also make sure some meta-packages are installed so the upgrade can continue without problems:

Update-manager

From version 6.06 and up you will need to install the update-manager and update-manager-core packages.

sudo aptitude install update-manager update-manager-core
Ubuntu-desktops

If you run a particular desktop version, you might want to reinstall this package to resolve any issue with dependencies of that package. You can (re)install these -desktop packages before or after your upgrade. To find out if you which desktop package you want to (re)install: `dpkg -l | grep tu-desktop`. Or search for one by running `aptitude search tu-desktop`. The correct commands to (re)install are:

# The Kubuntu desktop
sudo aptitude install kubuntu-desktop
# or
sudo aptitude reinstall kubuntu-desktop
Kernels
sudo aptitude install linux-image-generic linux-headers-generic
# or
sudo aptitude install linux-image-server linux-headers-server
# or
sudo aptitude install linux-image-virtual linux-headers-virtual
  • 5.04: linux-image-386 and linux-headers-386
sudo aptitude install linux-image-386 linux-headers-386
  • 4.10: linux-image-386 and linux-kernel-headers
sudo aptitude install linux-image-386 linux-kernel-headers

Known issues

Some issues are related to apt-get upgrade and dist-upgrade commands. If you get calculation errors when running do-release-upgrade you can resolve this issue by running `do-release-upgrade -m desktop` or you can remove the ubuntu-desktop package. When aptitude is used there is no need for this. Please follow the guide exactly, when this guide wants to use apt-get, it will tell you :) If you run into individual dependency issues you need to resolve these individually. You can use `sudo apt-get -f install` for this. And then continue by running e.g. `sudo ./feisty --frontend DistUpgradeViewTextm -mode=server`. Replace feisty with the release where you upgrade to, this will continue the do-release-upgrade process.

8.10 to 9.04 (Intrepid to Jaunty)

This upgrade exercise has been executed on a fresh install of Ubuntu 8.10 and we will upgrade to 9.04. Intrepid 8.10 to Jaunty 9.04:: EOLUpgrades/Intrepid

6.10 to 8.04 (Edgy to Hardy)

This upgrade exercise has been executed on a fresh install of Ubuntu 6.10 and we will upgrade to 8.04.3 LTS. Edgy 6.10 to Feisty 7.04:: EOLUpgrades/Edgy Feisty 7.04 to Gutsy 7.10:: EOLUpgrades/Feisty Gutsy 7.10 to Hardy 8.04:: EOLUpgrades/Gutsy

6.06 to 8.04.3 (Dapper to Hardy)

Dapper 6.06 to Hardy 8.04.3:: EOLUpgrades/Dapper

4.10 to 6.06 (Warty to Dapper)

This upgrade exercise has been executed on a fresh install of Ubuntu 4.10 and we will upgrade to 6.06.2 LTS. Warty 4.10 to Hoary 5.04:: EOLUpgrades/Warty Hoary 5.04 to Breezy 5.10:: EOLUpgrades/Hoary Breezy 5.10 to Dapper 6.06.2:: EOLUpgrades/Breezy

See Also

Upgrade path:

Bugs:

Comments

If you think something is incorrect on this page please contact me. You can find my contact details here. I would also like to hear from you if this guide didn't help you, the more feedback I get, the better this guide will get.