个人工具

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

来自Ubuntu中文

跳转至: 导航, 搜索
 
(未显示同一用户的5个中间版本)
第1行: 第1行:
 
{{From|https://help.ubuntu.com/community/DapperUpgrades}}
 
{{From|https://help.ubuntu.com/community/DapperUpgrades}}
 
{{Languages|UbuntuHelp:DapperUpgrades}}
 
{{Languages|UbuntuHelp:DapperUpgrades}}
 +
#title Upgrading to Ubuntu 6.06 LTS
 
== What is Ubuntu 6.06 LTS? ==
 
== What is Ubuntu 6.06 LTS? ==
Ubuntu 6.06 LTS is the current Long Term Support version of the Ubuntu operating system. It was released on June 1st, 2006. It will be supported until June 1st, 2009 on desktops and June 1st, 2011 on servers. The name given to this release is "Dapper Drake".
+
Ubuntu 6.06 LTS is a supported Long Term Support version of the Ubuntu operating system, although not the most recent LTS release. It was released on June 1st, 2006. It will be supported until June 1st, 2009 on desktops and June 1st, 2011 on servers. The name given to this release is "Dapper Drake".
 
http://www.ubuntu.com/news/606released
 
http://www.ubuntu.com/news/606released
 +
Upgrades to '''Ubuntu 6.06 LTS (codename "Dapper Drake")''' are only supported from '''Ubuntu 5.10 (codename "Breezy Badger")'''. If you are running a version other than 5.10, see [[UbuntuHelp:UpgradeNotes|UpgradeNotes]].
 +
Ubuntu 6.06 LTS may itself be upgraded directly to the most recent Long Term Service release, [[UbuntuHelp:HardyUpgrades|Ubuntu 8.04 LTS]].
 
== Before you start ... ==
 
== Before you start ... ==
 
Please check out the [http://ubuntuforums.org/forumdisplay.php?f=140 Installation and Upgrade Help section] of the [http://www.ubuntu.com/community/forums Ubuntu Web Forums], including specifically:
 
Please check out the [http://ubuntuforums.org/forumdisplay.php?f=140 Installation and Upgrade Help section] of the [http://www.ubuntu.com/community/forums Ubuntu Web Forums], including specifically:
第10行: 第13行:
 
== Upgrading from Ubuntu 5.10 ("Breezy Badger") ==
 
== Upgrading from Ubuntu 5.10 ("Breezy Badger") ==
 
There are two considerations to make when updating to Dapper.
 
There are two considerations to make when updating to Dapper.
# Whether you will
+
<ol><li>Whether you will</li></ol>
#* get all the latest software (as upgrade packages) from the internet at the time that you perform the upgrade, or
+
 
#** get a CD of the Dapper packages, and include it in the upgrade, so only a few packages that were released since the "Dapper" CD was produced need to be obtained from the internet at the time that you perform the upgrade.
+
* get all the latest software (as upgrade packages) from the internet at the time that you perform the upgrade, or
# Whether you will
+
* get a CD of the Dapper packages, and include it in the upgrade, so only a few packages that were released since the "Dapper" CD was produced need to be obtained from the internet at the time that you perform the upgrade.
#* use the standard package management tools already installed by default in Breezy, or
+
<ol><li>Whether you will</li></ol>
#** hack files and run commands from the command line.
+
 
 +
* use the standard package management tools already installed by default in Breezy, or
 +
* hack files and run commands from the command line.
 
You can upgrade using the GUI tools, and/or if so inclined, can edit configuration files and run upgrade programs from a command line.
 
You can upgrade using the GUI tools, and/or if so inclined, can edit configuration files and run upgrade programs from a command line.
 
These approaches are described more fully in the next sections.
 
These approaches are described more fully in the next sections.
 
=== Upgrading with the Update Manager application ===
 
=== Upgrading with the Update Manager application ===
 
This is the simplest way for most users, especially if you are not an expert.
 
This is the simplest way for most users, especially if you are not an expert.
# First, update your system to ensure that you have the latest version of "Update Manager" and associated packages. A new version of "Update Manager" that can upgrade your entire system from Breezy to Dapper in a few simple steps is released, and available from the "Breezy-Updates" package repository.
+
==== Fully updating 5.10 ====
#* Make sure your system is using this repository. Confirm that you have version "0.42.2ubuntu12~breezy1" or newer of Update-manager installed, using the "Synaptic Package Manager" application. You need to ensure that your system is aware of what the latest versions are. If your system is not automatically checking for the latest updates, turn it on or do it manually. (In Synaptic go to menu "Settings -> Repositories", then the "Settings" button.
+
Before upgrading to Ubuntu 6.06 LTS, you should make sure Ubuntu 5.10 is fully up to date. Ubuntu 5.10 does not have ongoing support and has now been removed from the normal archives and mirrors, but its packages are still available if you add these lines to your <code><nowiki>/etc/apt/sources.list</nowiki></code> file:
#** If the check box "Automatically check for software updates" is off,
+
<pre><nowiki>
#*** turn it on, or
+
deb http://old-releases.ubuntu.com/ubuntu/ breezy main restricted universe multiverse
#**** do it manually via either the "Reload" button or menu "Edit -> Reload Package Information").
+
deb http://old-releases.ubuntu.com/ubuntu/ breezy-updates main restricted universe multiverse
#*** Then, still in "Synaptic Package Manager",  update "Update Manager" to the latest version and quit "Synaptic Package Manager".
+
deb http://old-releases.ubuntu.com/ubuntu/ breezy-security main restricted universe multiverse
# Open the Update Manager from the System/Administration menu, or run the following command (either via ALT-F2 or a terminal):
+
</nowiki></pre>
 +
==== Installing Update Manager ====
 +
An Update Manager application that can update your system from 5.10 to 6.06 LTS is available from breezy-updates (from old-releases, above). Make sure your system is using this repository. Confirm that you have version "0.42.2ubuntu12~breezy1" or newer of update-manager installed, using the "Synaptic Package Manager" application. You need to ensure that your system is aware of what the latest versions are. If your system is not automatically checking for the latest updates, turn it on or do it manually. (In Synaptic go to menu "Settings -> Repositories", then the "Settings" button.
 +
* If the check box "Automatically check for software updates" is off,
 +
* turn it on, or
 +
* do it manually via either the "Reload" button or menu "Edit -> Reload Package Information").
 +
* Then, still in "Synaptic Package Manager",  update "Update Manager" to the latest version and quit "Synaptic Package Manager".
 +
==== Performing the upgrade with Update Manager ====
 +
<ol><li>Open the Update Manager from the System/Administration menu, or run the following command (either via ALT-F2 or a terminal):</li></ol>
 +
 
 
<pre><nowiki>
 
<pre><nowiki>
 
  gksudo "update-manager" </nowiki></pre>
 
  gksudo "update-manager" </nowiki></pre>
第34行: 第48行:
 
=== Upgrading by changing sources and the command line ===
 
=== Upgrading by changing sources and the command line ===
 
If you are using Kubuntu and don't want to download the GTK applications required for the update manager, or you don't wish to use the update manager for any other reason, then follow this process for upgrading to Dapper (Ubuntu 6.06) from Breezy (Ubuntu 5.10).
 
If you are using Kubuntu and don't want to download the GTK applications required for the update manager, or you don't wish to use the update manager for any other reason, then follow this process for upgrading to Dapper (Ubuntu 6.06) from Breezy (Ubuntu 5.10).
# Make sure that you have ubuntu-desktop, kubuntu-desktop, or edubuntu-desktop installed (depending on which distribution you are using). '''This is VITAL for apt to perform the upgrade successfully.'''
+
<ol><li>Make sure that you have ubuntu-desktop, kubuntu-desktop, or edubuntu-desktop installed (depending on which distribution you are using). '''This is VITAL for apt to perform the upgrade successfully.'''
2. If you have both xscreensaver and gnome-screensaver installed, you will need to remove xscreensaver to avoid a dependency conflict between the two. Enter the following into a terminal to remove the package:
+
</li><li>If you have both xscreensaver and gnome-screensaver installed, you will need to remove xscreensaver to avoid a dependency conflict between the two. Enter the following into a terminal to remove the package:</li></ol>
 +
 
 
<pre><nowiki>
 
<pre><nowiki>
 
  sudo apt-get remove xscreensaver </nowiki></pre>
 
  sudo apt-get remove xscreensaver </nowiki></pre>
3. Edit your /etc/apt/sources.list as root:
+
<ol><li>Edit your /etc/apt/sources.list as root:</li></ol>
 +
 
 
<pre><nowiki>
 
<pre><nowiki>
 
  kdesu kate /etc/apt/sources.list </nowiki></pre>
 
  kdesu kate /etc/apt/sources.list </nowiki></pre>
第73行: 第89行:
 
*. Make sure you type <code><nowiki> dist-upgrade </nowiki></code> rather than <code><nowiki> upgrade </nowiki></code>, because <code><nowiki> upgrade </nowiki></code> will totally hose your machine and render it '''completely unbootable'''. This is because a normal upgrade won´t upgrade packages with uninstalled dependencies, meaning your system will end up half Breezy and half Dapper.
 
*. Make sure you type <code><nowiki> dist-upgrade </nowiki></code> rather than <code><nowiki> upgrade </nowiki></code>, because <code><nowiki> upgrade </nowiki></code> will totally hose your machine and render it '''completely unbootable'''. This is because a normal upgrade won´t upgrade packages with uninstalled dependencies, meaning your system will end up half Breezy and half Dapper.
 
=== Upgrading from an Ubuntu 6.06 CD ===
 
=== Upgrading from an Ubuntu 6.06 CD ===
# Make sure that you have the package "ubuntu-desktop" or "kubuntu-desktop" or "edubuntu-desktop" installed (depending on the distribution you are using).
+
<ol><li>Make sure that you have the package "ubuntu-desktop" or "kubuntu-desktop" or "edubuntu-desktop" installed (depending on the distribution you are using).
# Edit your /etc/apt/sources.list as root:
+
</li><li>Edit your /etc/apt/sources.list as root:</li></ol>
 +
 
 
For Ubuntu/Xubuntu:
 
For Ubuntu/Xubuntu:
 
<pre><nowiki>
 
<pre><nowiki>
第82行: 第99行:
 
   kdesu kate /etc/apt/sources.list </nowiki></pre>
 
   kdesu kate /etc/apt/sources.list </nowiki></pre>
 
and change every occurrence of "breezy" to "dapper".
 
and change every occurrence of "breezy" to "dapper".
# either
+
<ol><li>either</li></ol>
#* Download the ISO image for the "Alternate Install CD", ('''not''' the "Desktop CD", which from my experience today 9th June and that of others in the [http://www.ubuntuforums.org/forumdisplay.php?f=140 web forum] is defective anyway, giving [http://www.ubuntuforums.org/showthread.php?t=192136 all sorts of problems], '''nor''' the "Server install CD"), eg from [http://www.ubuntu.com/download here] or from [http://torrent.ubuntu.com:6969/ Torrents] and burn it to CD, or,
+
 
#** Order the (3) CDs to be posted out to you via [https://shipit.ubuntu.com/ ShipIt], and use the "Alternate Install CD".
+
* Download the ISO image for the "Alternate Install CD", ('''not''' the "Desktop CD", which from my experience today 9th June and that of others in the [http://www.ubuntuforums.org/forumdisplay.php?f=140 web forum] is defective anyway, giving [http://www.ubuntuforums.org/showthread.php?t=192136 all sorts of problems], '''nor''' the "Server install CD"), eg from [http://www.ubuntu.com/download here] or from [http://torrent.ubuntu.com:6969/ Torrents] and burn it to CD, or,
# To install from a physical CD
+
* Order the (3) CDs to be posted out to you via [https://shipit.ubuntu.com/ ShipIt], and use the "Alternate Install CD".
## Run:
+
<ol><li>To install from a physical CD
 +
<ol><li>Run:</li></ol>
 +
 
 
<pre><nowiki>
 
<pre><nowiki>
 
     sudo apt-cdrom add </nowiki></pre>
 
     sudo apt-cdrom add </nowiki></pre>
 
Insert the CD, and press enter.
 
Insert the CD, and press enter.
# Run:
+
<ol><li>Run:</li></ol>
 +
 
 
<pre><nowiki>
 
<pre><nowiki>
 
     sudo apt-get update && sudo apt-get dist-upgrade </nowiki></pre>
 
     sudo apt-get update && sudo apt-get dist-upgrade </nowiki></pre>
# To install directly from the ISO image
+
<ol><li>To install directly from the ISO image
## Mount the ISO to /cdrom:
+
<ol><li>Mount the ISO to /cdrom:</li></ol>
 +
 
 
<pre><nowiki>
 
<pre><nowiki>
 
     sudo mount -t iso9660 ubuntu-6.06-alternate-i386.iso /cdrom -o loop </nowiki></pre>
 
     sudo mount -t iso9660 ubuntu-6.06-alternate-i386.iso /cdrom -o loop </nowiki></pre>
 
Using the full path and proper name for the ISO image
 
Using the full path and proper name for the ISO image
# Run:
+
<ol><li>Run:</li></ol>
 +
 
 
<pre><nowiki>
 
<pre><nowiki>
 
     sudo apt-cdrom -m add </nowiki></pre>
 
     sudo apt-cdrom -m add </nowiki></pre>
# Run:
+
<ol><li>Run:</li></ol>
 +
 
 
<pre><nowiki>
 
<pre><nowiki>
 
     sudo apt-get update && sudo apt-get dist-upgrade </nowiki></pre>
 
     sudo apt-get update && sudo apt-get dist-upgrade </nowiki></pre>
# Unmount the ISO
+
<ol><li>Unmount the ISO</li></ol>
 +
 
 
<pre><nowiki>
 
<pre><nowiki>
 
     sudo umount /cdrom </nowiki></pre>
 
     sudo umount /cdrom </nowiki></pre>
== Upgrading from Ubuntu releases prior to 5.10 ==
 
# Upgrade to Ubuntu 5.10 (see [[UbuntuHelp:BreezyUpgradeNotes|BreezyUpgradeNotes]])
 
# Follow the above instructions for upgrading from 5.10
 
 
== Upgrading from Ubuntu Dapper betas ==
 
== Upgrading from Ubuntu Dapper betas ==
 
If you are a tester or have been tracking updates to pre-release Dapper via APT then congratulations, your updates after June 1 will now bring you up to date with Ubuntu 6.06 LTS "Dapper" final.
 
If you are a tester or have been tracking updates to pre-release Dapper via APT then congratulations, your updates after June 1 will now bring you up to date with Ubuntu 6.06 LTS "Dapper" final.
第121行: 第142行:
 
* Check your /var/log/Xorg.0.log and ~/xsession-errors log files.
 
* Check your /var/log/Xorg.0.log and ~/xsession-errors log files.
 
* Check that you have the "breezy-updates" repository enabled. It can be enabled from the Synaptic package manager or by editing /etc/apt/sources.list with a text editor.
 
* Check that you have the "breezy-updates" repository enabled. It can be enabled from the Synaptic package manager or by editing /etc/apt/sources.list with a text editor.
 +
* Check that your /etc/apt/sources.list.d directory is available and properly owned by root.  If it is not then the upgrade will fail silently and mysteriously.
 
=== PCMCIA Services Hang ===
 
=== PCMCIA Services Hang ===
 
There is a bug that causes some upgrades to hang on non-PCMCIA machines while setting up the PCMCIA services.  Further, once this happens, the boot process of the machine will always hang at the point of starting PCMCIA services; this happens even when booting in recovery mode.  The bug report is [https://launchpad.net/distros/ubuntu/+source/linux-source-2.6.15/+bug/35140 here]
 
There is a bug that causes some upgrades to hang on non-PCMCIA machines while setting up the PCMCIA services.  Further, once this happens, the boot process of the machine will always hang at the point of starting PCMCIA services; this happens even when booting in recovery mode.  The bug report is [https://launchpad.net/distros/ubuntu/+source/linux-source-2.6.15/+bug/35140 here]
 
A fix for this problem is in the `dapper-updates` repository. We '''strongly''' recommend that upgraders enable `dapper-updates` while upgrading. This will make the workaround below unnecessary.
 
A fix for this problem is in the `dapper-updates` repository. We '''strongly''' recommend that upgraders enable `dapper-updates` while upgrading. This will make the workaround below unnecessary.
 
The workaround for this bug is as follows (this worked for me; I can make no guarantees about other computers -- USE AT YOUR OWN RISK):
 
The workaround for this bug is as follows (this worked for me; I can make no guarantees about other computers -- USE AT YOUR OWN RISK):
# Reboot using a bootable rescue CD.  I recommend the Ubuntu Live CD,[http://sysresccd.org/ System Rescue CD], or [http://www.knopper.net/knoppix/index-en.html Knoppix].
+
<ol><li>Reboot using a bootable rescue CD.  I recommend the Ubuntu Live CD,[http://sysresccd.org/ System Rescue CD], or [http://www.knopper.net/knoppix/index-en.html Knoppix].
# Mount the partition containing /etc (usually your root filesystem) read-write.  A typical command sequence for this would be
+
</li><li>Mount the partition containing /etc (usually your root filesystem) read-write.  A typical command sequence for this would be</li></ol>
 +
 
 
<pre><nowiki>
 
<pre><nowiki>
 
   mkdir /mnt/hda1
 
   mkdir /mnt/hda1
 
   mount /dev/hda1 /mnt/hda1 -o rw </nowiki></pre>
 
   mount /dev/hda1 /mnt/hda1 -o rw </nowiki></pre>
# Move the files <code><nowiki> etc/init.d/pcmcia </nowiki></code> and <code><nowiki> etc/init.d/pcmciautils </nowiki></code> somewhere else (to keep them from executing on startup).  A typical command sequence for this would be:
+
<ol><li>Move the files <code><nowiki> etc/init.d/pcmcia </nowiki></code> and <code><nowiki> etc/init.d/pcmciautils </nowiki></code> somewhere else (to keep them from executing on startup).  A typical command sequence for this would be:</li></ol>
 +
 
 
<pre><nowiki>
 
<pre><nowiki>
 
   cd /mnt/hda1/etc
 
   cd /mnt/hda1/etc
 
   mv init.d/pcmcia pcmcia.bak
 
   mv init.d/pcmcia pcmcia.bak
 
   mv init.d/pcmciautils pcmciautils.bak </nowiki></pre>
 
   mv init.d/pcmciautils pcmciautils.bak </nowiki></pre>
# Remove the CD, and boot your computer from the hard disk.
+
<ol><li>Remove the CD, and boot your computer from the hard disk.
# Before logging in, in the bottom left corner, select Options -> Sessions -> GNOME.  When asked whether to change this to the default session, say "No". (This step is necessary because the unfinished setup process rendered the default session unusable.)
+
</li><li>Before logging in, in the bottom left corner, select Options -> Sessions -> GNOME.  When asked whether to change this to the default session, say "No". (This step is necessary because the unfinished setup process rendered the default session unusable.)
# Open a terminal and run
+
</li><li>Open a terminal and run</li></ol>
 +
 
 
<code><nowiki> sudo dpkg --configure -a </nowiki></code>
 
<code><nowiki> sudo dpkg --configure -a </nowiki></code>
 
(you can't use synaptic or the updater for this, they're both broken in the current system state). If you watch the terminal, the attempt to setup the package pcmcia-cs will fail because it can't find the file we moved; this is OK. Wait for the configure to finish; it will take a long time.
 
(you can't use synaptic or the updater for this, they're both broken in the current system state). If you watch the terminal, the attempt to setup the package pcmcia-cs will fail because it can't find the file we moved; this is OK. Wait for the configure to finish; it will take a long time.
# (Optional) Move the pcmcia init scripts back with
+
<ol><li>(Optional) Move the pcmcia init scripts back with</li></ol>
 +
 
 
<pre><nowiki>
 
<pre><nowiki>
 
   mv /etc/pcmcia.bak /etc/init.d/pcmcia
 
   mv /etc/pcmcia.bak /etc/init.d/pcmcia
 
   mv /etc/pcmciautils.bak /etc/init.d/pcmciautils </nowiki></pre>
 
   mv /etc/pcmciautils.bak /etc/init.d/pcmciautils </nowiki></pre>
 
Now that the setup is finished, they will no longer hang the machine (but if this bug is affecting you, they won't do anything either, so it doesn't matter either way).
 
Now that the setup is finished, they will no longer hang the machine (but if this bug is affecting you, they won't do anything either, so it doesn't matter either way).
# Reboot the machine.  It should boot normally now (into Dapper!).  You can now run
+
<ol><li>Reboot the machine.  It should boot normally now (into Dapper!).  You can now run</li></ol>
 +
 
 
<pre><nowiki>
 
<pre><nowiki>
 
   sudo apt-get -f install
 
   sudo apt-get -f install
第166行: 第193行:
 
When the package is reinstalled, the header files are correctly installed in
 
When the package is reinstalled, the header files are correctly installed in
 
/usr/include/GL.
 
/usr/include/GL.
(See, for example,  LaunchPad bugs #29435 and #40951.)
+
(See, for example,  launchpad bugs #29435 and #40951.)
 
----
 
----
[[category:CategoryDocumentation]]
+
[[category:CategoryUpgrade]]
  
 
[[category:UbuntuHelp]]
 
[[category:UbuntuHelp]]

2009年11月17日 (二) 18:50的最新版本

  1. title Upgrading to Ubuntu 6.06 LTS

What is Ubuntu 6.06 LTS?

Ubuntu 6.06 LTS is a supported Long Term Support version of the Ubuntu operating system, although not the most recent LTS release. It was released on June 1st, 2006. It will be supported until June 1st, 2009 on desktops and June 1st, 2011 on servers. The name given to this release is "Dapper Drake". http://www.ubuntu.com/news/606released Upgrades to Ubuntu 6.06 LTS (codename "Dapper Drake") are only supported from Ubuntu 5.10 (codename "Breezy Badger"). If you are running a version other than 5.10, see UpgradeNotes. Ubuntu 6.06 LTS may itself be upgraded directly to the most recent Long Term Service release, Ubuntu 8.04 LTS.

Before you start ...

Please check out the Installation and Upgrade Help section of the Ubuntu Web Forums, including specifically:

Upgrading from Ubuntu 5.10 ("Breezy Badger")

There are two considerations to make when updating to Dapper.

  1. Whether you will
  • get all the latest software (as upgrade packages) from the internet at the time that you perform the upgrade, or
  • get a CD of the Dapper packages, and include it in the upgrade, so only a few packages that were released since the "Dapper" CD was produced need to be obtained from the internet at the time that you perform the upgrade.
  1. Whether you will
  • use the standard package management tools already installed by default in Breezy, or
  • hack files and run commands from the command line.

You can upgrade using the GUI tools, and/or if so inclined, can edit configuration files and run upgrade programs from a command line. These approaches are described more fully in the next sections.

Upgrading with the Update Manager application

This is the simplest way for most users, especially if you are not an expert.

Fully updating 5.10

Before upgrading to Ubuntu 6.06 LTS, you should make sure Ubuntu 5.10 is fully up to date. Ubuntu 5.10 does not have ongoing support and has now been removed from the normal archives and mirrors, but its packages are still available if you add these lines to your /etc/apt/sources.list file:

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

Installing Update Manager

An Update Manager application that can update your system from 5.10 to 6.06 LTS is available from breezy-updates (from old-releases, above). Make sure your system is using this repository. Confirm that you have version "0.42.2ubuntu12~breezy1" or newer of update-manager installed, using the "Synaptic Package Manager" application. You need to ensure that your system is aware of what the latest versions are. If your system is not automatically checking for the latest updates, turn it on or do it manually. (In Synaptic go to menu "Settings -> Repositories", then the "Settings" button.

  • If the check box "Automatically check for software updates" is off,
  • turn it on, or
  • do it manually via either the "Reload" button or menu "Edit -> Reload Package Information").
  • Then, still in "Synaptic Package Manager", update "Update Manager" to the latest version and quit "Synaptic Package Manager".

Performing the upgrade with Update Manager

  1. Open the Update Manager from the System/Administration menu, or run the following command (either via ALT-F2 or a terminal):
 gksudo "update-manager" 

Click the "Check" button. If you have a working network connection, it should then inform you about the new release of Dapper, and offer to upgrade your system to it. When you start the upgrade, packages will soon be downloading and you should see a progress bar with time remaining. This is the time remaining to get the packages, not to complete the update, and may not be accurate. When it finishes the packages will begin installing. You should shortly see a new time remaining. If you don't (and this does happen) you should select the "terminal>" expander as the configuration is likely asking you a question, or prompting you to continue. Most likely you can just press enter. Note that the upgrade will not continue until you do.

Upgrading by changing sources and the command line

If you are using Kubuntu and don't want to download the GTK applications required for the update manager, or you don't wish to use the update manager for any other reason, then follow this process for upgrading to Dapper (Ubuntu 6.06) from Breezy (Ubuntu 5.10).

  1. Make sure that you have ubuntu-desktop, kubuntu-desktop, or edubuntu-desktop installed (depending on which distribution you are using). This is VITAL for apt to perform the upgrade successfully.
  2. If you have both xscreensaver and gnome-screensaver installed, you will need to remove xscreensaver to avoid a dependency conflict between the two. Enter the following into a terminal to remove the package:
 sudo apt-get remove xscreensaver 
  1. Edit your /etc/apt/sources.list as root:
 kdesu kate /etc/apt/sources.list 

Or if you're using GNOME/XFCE:

 gksudo "gedit /etc/apt/sources.list" 

And change every occurrence of "breezy" to "dapper"; if you have a CD-ROM line in your file, then remove it. Your sources.list should look something like this, now:

 ## All officially supported packages, including security- and other updates
 deb http://archive.ubuntu.com/ubuntu dapper main restricted
 deb http://security.ubuntu.com/ubuntu dapper-security main restricted
 deb http://archive.ubuntu.com/ubuntu dapper-updates main restricted

 ## The source packages (only needed to recompile existing packages)
 #deb-src http://archive.ubuntu.com/ubuntu dapper main restricted
 #deb-src http://security.ubuntu.com/ubuntu dapper-security main restricted
 #deb-src http://archive.ubuntu.com/ubuntu dapper-updates main restricted

 ## All community supported packages, including security- and other updates
 deb http://archive.ubuntu.com/ubuntu dapper universe multiverse
 deb http://security.ubuntu.com/ubuntu dapper-security universe multiverse
 deb http://archive.ubuntu.com/ubuntu dapper-updates universe multiverse

 ## The source packages (only needed to recompile existing packages)
 #deb-src http://archive.ubuntu.com/ubuntu dapper universe multiverse
 #deb-src http://security.ubuntu.com/ubuntu dapper-security universe multiverse
 #deb-src http://archive.ubuntu.com/ubuntu dapper-updates universe multiverse
 

Then:

 sudo apt-get update && sudo apt-get dist-upgrade 

EXTREMELY IMPORTANT:

  • . Enter the command exactly as above, so the dist-upgrade step will run only if the update step is successful. If the first step fails but you still attempt to run the second step, you will probably end up with a corrupted system.
  • . Make sure you type dist-upgrade rather than upgrade , because upgrade will totally hose your machine and render it completely unbootable. This is because a normal upgrade won´t upgrade packages with uninstalled dependencies, meaning your system will end up half Breezy and half Dapper.

Upgrading from an Ubuntu 6.06 CD

  1. Make sure that you have the package "ubuntu-desktop" or "kubuntu-desktop" or "edubuntu-desktop" installed (depending on the distribution you are using).
  2. Edit your /etc/apt/sources.list as root:

For Ubuntu/Xubuntu:

   gksudo "gedit /etc/apt/sources.list" 

or for Kubuntu:

   kdesu kate /etc/apt/sources.list 

and change every occurrence of "breezy" to "dapper".

  1. either
  • Download the ISO image for the "Alternate Install CD", (not the "Desktop CD", which from my experience today 9th June and that of others in the web forum is defective anyway, giving all sorts of problems, nor the "Server install CD"), eg from here or from Torrents and burn it to CD, or,
  • Order the (3) CDs to be posted out to you via ShipIt, and use the "Alternate Install CD".
  1. To install from a physical CD
    1. Run:
         sudo apt-cdrom add 

    Insert the CD, and press enter.

    1. Run:
         sudo apt-get update && sudo apt-get dist-upgrade 
    1. To install directly from the ISO image
      1. Mount the ISO to /cdrom:
           sudo mount -t iso9660 ubuntu-6.06-alternate-i386.iso /cdrom -o loop 

      Using the full path and proper name for the ISO image

      1. Run:
           sudo apt-cdrom -m add 
      1. Run:
           sudo apt-get update && sudo apt-get dist-upgrade 
      1. Unmount the ISO
           sudo umount /cdrom 

      Upgrading from Ubuntu Dapper betas

      If you are a tester or have been tracking updates to pre-release Dapper via APT then congratulations, your updates after June 1 will now bring you up to date with Ubuntu 6.06 LTS "Dapper" final.

      Troubleshooting

      • In the unlikely event you encounter some problems, double check that your required meta package is installed for your flavor. For Ubuntu this is 'ubuntu-desktop', for Kubuntu 'kubuntu-desktop', etc.
      • Ensure all necessary packages are completely installed and configured by issuing these commands (via ALT+F2 if necessary):
        sudo apt-get -f install
        sudo dpkg --configure -a
        
      • Check your /var/log/Xorg.0.log and ~/xsession-errors log files.
      • Check that you have the "breezy-updates" repository enabled. It can be enabled from the Synaptic package manager or by editing /etc/apt/sources.list with a text editor.
      • Check that your /etc/apt/sources.list.d directory is available and properly owned by root. If it is not then the upgrade will fail silently and mysteriously.

      PCMCIA Services Hang

      There is a bug that causes some upgrades to hang on non-PCMCIA machines while setting up the PCMCIA services. Further, once this happens, the boot process of the machine will always hang at the point of starting PCMCIA services; this happens even when booting in recovery mode. The bug report is here A fix for this problem is in the `dapper-updates` repository. We strongly recommend that upgraders enable `dapper-updates` while upgrading. This will make the workaround below unnecessary. The workaround for this bug is as follows (this worked for me; I can make no guarantees about other computers -- USE AT YOUR OWN RISK):

      1. Reboot using a bootable rescue CD. I recommend the Ubuntu Live CD,System Rescue CD, or Knoppix.
      2. Mount the partition containing /etc (usually your root filesystem) read-write. A typical command sequence for this would be
        mkdir /mnt/hda1
        mount /dev/hda1 /mnt/hda1 -o rw 
      1. Move the files etc/init.d/pcmcia and etc/init.d/pcmciautils somewhere else (to keep them from executing on startup). A typical command sequence for this would be:
         cd /mnt/hda1/etc
         mv init.d/pcmcia pcmcia.bak
         mv init.d/pcmciautils pcmciautils.bak 
      1. Remove the CD, and boot your computer from the hard disk.
      2. Before logging in, in the bottom left corner, select Options -> Sessions -> GNOME. When asked whether to change this to the default session, say "No". (This step is necessary because the unfinished setup process rendered the default session unusable.)
      3. Open a terminal and run

      sudo dpkg --configure -a (you can't use synaptic or the updater for this, they're both broken in the current system state). If you watch the terminal, the attempt to setup the package pcmcia-cs will fail because it can't find the file we moved; this is OK. Wait for the configure to finish; it will take a long time.

      1. (Optional) Move the pcmcia init scripts back with
         mv /etc/pcmcia.bak /etc/init.d/pcmcia
         mv /etc/pcmciautils.bak /etc/init.d/pcmciautils 

      Now that the setup is finished, they will no longer hang the machine (but if this bug is affecting you, they won't do anything either, so it doesn't matter either way).

      1. Reboot the machine. It should boot normally now (into Dapper!). You can now run
         sudo apt-get -f install
         sudo dpkg --configure -a 

      just to be safe, but they should do nothing. Congratulations, your system is fixed!

      After You Upgrade

      After you have upgraded to Dapper, check your packages to see if you have the package mesa-common-dev installed. If so, you should reinstall this package. You may do this in Synaptic Package Manager or on the command line. In Synaptic: search for mesa-common-dev, right-click on the package name, select Mark for Reinstallation, and then click on the Apply button. If you prefer the command line, you can reinstall the package with

         sudo apt-get install --reinstall mesa-common-dev 

      Why is this necessary? It appears that when mesa-common-dev is installed during the upgrade from breezy to dapper, it fails to install several C header files in /usr/include/GL. (This will only matter to you if you try to compile OpenGL programs.) When the package is reinstalled, the header files are correctly installed in /usr/include/GL. (See, for example, launchpad bugs #29435 and #40951.)