Differences between revisions 21 and 22
Revision 21 as of 2007-03-24 23:16:15
Size: 3471
Comment: Mention some problems
Revision 22 as of 2007-03-24 23:17:24
Size: 3472
Editor: ?SteveLangasek
Comment:
Deletions are marked like this. Additions are marked like this.
Line 7: Line 7:
$(COLUMNS=180 dpkg -l 'kernel-image-2.6*' | awk '/^ii/ { print $2 }) }}} $(COLUMNS=180 dpkg -l 'kernel-image-2.6*' | awk '/^ii/ { print $2 }') }}}

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"

  • {{{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
  • if a 2.6 kernel is installed:?BRaptitude unmarkauto kernel-image-2.6.8-[<abi>-]<flavor>

    • check which kernels are installed with?BRdpkg -l kernel-image-* | grep ^ii

    • needed because otherwise the dist-upgrade may try to uninstall it 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

  • aptitude update (get gpg sigs)

    • if using lilo and not updated, the system will not boot from here on
  • aptitude install linux-image-2.6-*

    • if not already pulled in by a kernel-image meta package
    • check which kernels are installed with?BRdpkg -l *-image-* | grep ^ii

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

Some cleanup which will easy etch->lenny upgrades:

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

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

Test case 1

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

Package set

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

  • apt-get install lvm2 kernel-image-2.6-686 (to avoid recommends)
  • aptitude markauto kernel-image-2.6.8-3-686
  • tasksel install desktop

Results

Success. 149 packages removed; mostly sarge-only, except for 46 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. Exceptions: akode, bc?

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?