Differences between revisions 41 and 42
Revision 41 as of 2007-03-25 22:17:30
Size: 6626
Editor: ?FransPop
Comment: Workaround for conflicts found!
Revision 42 as of 2007-03-25 22:40:37
Size: 6620
Editor: ?FransPop
Comment: Server upgrade now successful
Deletions are marked like this. Additions are marked like this.
Line 98: Line 98:
Not yet success. Success.
Line 112: Line 112:
Reason X11 (and even some bits of Gnome) is installed is that some Sarge server tasks depend on graphical management tools. Because the X installation is less complete than for desktop, x11-common needs to be added to the manually installed packages to avoid conflicts. Reason X11 (and even some bits of Gnome) is installed is that some Sarge server tasks depend on graphical management tools. Because the X11 installation is less complete than for desktop, x11-common needs to be added to the manually installed packages to avoid conflicts.

This page exists as an aid for working through the issues with the sarge->etch upgrade path, by providing a current picture of the recommended approaches, and their pros and cons.

See also the [http://lists.debian.org/debian-release/2007/03/msg00776.html latest discussion] on the mailing lists.

Method "C"

  • Run aptitude interactively and check that there are no packages scheduled for removal or update (if a packages were installed with apt-get, aptitude may sometimes not know about it and list it for removal; in general, the system should be up-to-date and "clean").
  • aptitude unmarkauto openoffice.org vim \
       $(COLUMNS=180 dpkg -l 'kernel-image-2.6*' | \
         awk '/^ii/ { print $2 }')
    • for desktop installs openoffice.org used to be pulled in by openoffice.org-bin which no longer exists
    • for desktop installs vim used to be pulled in through vim-gtk, but apparently nothing depends on that anymore
    • for 2.6 kernel images this is needed because otherwise the dist-upgrade may try to uninstall them if the kernel was installed through a kernel-image meta package
  • edit sources.list to point to Etch
  • aptitude update

    • we should warn about the "errors" aptitude insists on printing here
  • aptitude upgrade

    • could also be switched with next step; advantage of doing the next step early could be that glibc is upgraded early; OTOH, doing easy/safe stuff first also makes sense
  • aptitude install initrd-tools libfam0 xlibmesa-glu

    • all if already installed
    • last two not needed if fixed in Etch
    • might be easier to setup two paths: desktop and non-desktop aggregating this and the unmarkauto openoffice
  • aptitude dist-upgrade

    • users of the 2.6 kernel wishing to test the kernel upgrade first should be advised to do the upgrade before this (as they might get the new kernel in this step) they will need to upgrade coreutils and udev before their ugprades. Users of 2.4 kernel can wait until after this.
    • if using lilo and it is not rerun after this, the system will not boot from here on
    • if using 2.6, and the kernel has not been upgrade, the system will not bootup properly (due to new udev)
    • if the system is rebooted midway through the process it might be unbootable or boot with errors
  • aptitude update (get gpg sigs)

  • aptitude install linux-image-2.6-*

    • in standard installs not need, it will have been pulled already in by a kernel-image meta package
    • check which kernels are installed with?BRdpkg -l *-image-* | grep ^ii

Recommended postinstall steps

  • aptitude purge hotplug

  • if using grub edit /etc/kernel-img.conf (not doing so could break upgrades to lenny)
  • if using lilo, run lilo

Some cleanup which will ease etch->lenny upgrades:

  • aptitude unmarkauto linux-image-2.6-<flavor>

  • aptitude purge kernel-image-2.6-<flavor>

Various cleanup:

  • remove gcc-3.3, g++-3.3 and related packages (etch uses 4.1 by default)
  • remove dummy packages; you may need to 'unmarkauto' the new packages that depend on the dummy packages
    • we could provide a list of dummy packages based on RN's find-dummies script
  • purge removed packages to remove configuration files

Test case 1 (vorlon)

Package set

sarge chroot built with Prio: standard and above, with these additions:

  • apt-get install lvm2 kernel-image-2.4.27-3-686
  • tasksel install desktop

Results

Success. 151 packages removed; all sarge-only, except for akode and hotplug. (XXX: may not be correct, I think I missed reviewing the block of "unused" removals)

Test case 2 (vorlon)

Package set

  • debootstrap --arch i386 sarge
  • aptitude install ~pstandard
  • aptitude install lvm2 kernel-image-2.6-686
  • tasksel install desktop

Results

Success. 145 packages removed; mostly sarge-only, except for 48 packages; most of these are auto-installed packages, either libs or other packages that are no longer part of the desktop task; or they are dummy packages not needed after upgrade.

Problems

This doesn't guarantee a usable kernel is installed at all points in the upgrade (if using 2.6); at some point in the dist-upgrade, udev is installed and hotplug is removed, leaving the previous kernel without working hotplug support, and the new kernel is not yet installed.

Also, there is a big udev warning asking you to purge hotplug. Will it interfere?

  • -- users should be reminded in the release notes to manually purge hotplug after upgrade. ?SteveLangasek

Test case 3 (fjp)

Package set

Standard current Sarge desktop install with both 2.4 and 2.6 kernel installed; running 2.6 during upgrade.

Results

Success. In total 1108 packages upgraded/installed and 145 removed.

Almost all removed packages were sarge only, pseudo packages or libraries. Exceptions:

gcc-3.4-base, g++-3.3

etch uses 4.1

hotplug

conflicts with udev

gstreamer0.8-*

superseded by gstreamer0.10

pkg-config

was dependency from gstreamer

bluefish

apparently dropped from gnome desktop task

gnome-doc-tools

was dependency from yelp (gnome help browser)

docbook-dsssl

was dependency from gnome-doc-tools

openjade

was dependency from docbook-dsssl

xmms

was dependency from kicker-applets and nautilus

Test case 4 (fjp)

Package set

Standard current Sarge install with all server tasks selected and both 2.4 and 2.6 kernel installed; running 2.6 during upgrade.

Results

Success.

For most server installs it will probably be possible to do the kernel installation much earlier. With all standard server tasks installed, I could do:

  • aptitude unmarkauto kernel-image-2.6.8-686

  • edit sources.list to point to Etch
  • aptitude update

  • aptitude install coreutils initrd-tools linux-image-2.6-686

The addition of initrd-tools in the 3rd step is needed to prevent removal of existing kernels; coreutils is needed to prevent the "readlink error". This step will also update libc6, install udev and remove base-config and hotplug.

The next steps are:

  • aptitude install libfam0 xlibmesa-glu x11-common

  • aptitude dist-upgrade

Reason X11 (and even some bits of Gnome) is installed is that some Sarge server tasks depend on graphical management tools. Because the X11 installation is less complete than for desktop, x11-common needs to be added to the manually installed packages to avoid conflicts.