DapperUpgrades

Revision 31 as of 2006-06-05 05:33:31

What is Ubuntu 6.06 LTS?

Ubuntu 6.06 LTS is the currrent version of the Ubuntu operating system, which was released June 1st, 2006.

http://www.ubuntu.com/news/606released

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.

Upgrading from Ubuntu 5.10 ("Breezy Badger")

There are a few ways you can get Dapper:

Upgrading with the Update Manager
Upgrading by changing sources and the command line
Downloading an ISO and burning a CD. You must use the alternate CD, not the desktop one, in order to upgrade. Torrents: http://torrent.ubuntu.com:6969/

Upgrading with the Update Manager

A new version of the Update Manager application has entered breezy-updates which can upgrade your entire system in a few simple steps.

To perform the upgrade:

First, update your system to ensure that you have the latest version of Update Manager and associated packages. You can do this using Update Manager itself, to be found under the System/Administration menu.
The necessary versions are available from the breezy-updates repository. Confirm that you have version 0.42.2ubuntu12~breezy1 or newer of update-manager installed by using the Synaptic Package Manager .

Then follow the steps below:

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"
```

2. Click the "Check" button.

If you have a working network connection, it should then inform you about a new release and offer to upgrade your system.

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. 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". Then:

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

EXTREMELY IMPORTANT! Make sure you type dist-upgrade rather than upgrade . The process will totally hose your machine and render it *completely unbootable* otherwise.

Upgrading from an Ubuntu 6.06 CD

Note that you cannot upgrade from the Desktop CD, only the Alternate CD!

1. Make sure that you have ubuntu-desktop, 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".

3. Run:

```
  sudo apt-cdrom add
```
insert the CD, and press enter.

4. Run:

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

Upgrading from Ubuntu releases prior to 5.10

Upgrade to Ubuntu 5.10 (see BreezyUpgradeNotes)
Follow the above instructions for upgrading from 5.10

Troubleshooting

In the unlikely event you encouter 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.

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]

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].
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  
```
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  
```
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.)
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.
(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).
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!

CategoryDocumentation

Ubuntu Wiki