Desktop upgrade report / aptitude from sid
Hello,
I upgraded my desktop system last night from sarge to etch, and at the
end it went very well. After a single reboot the new kernel, xorg, and
KDE came up. Impressive that it run for hours and it came in a very
usable state.
There have been a few glitches during the upgrade though, which I was
able to fix. I want to share my upgrade summary, hope it helps to make etch
even better.
Thanks,
Rainer
Desktop upgrade report
======================
Starting point:
---------------
This desktop was upgraded from woody before, i.e. no sarge
install. And it had packages from backports.org
After I saw there are concerns against aptitude from unstable, because
it saw little testing, I selected aptitude from unstable for the
upgrade. Note that I have sid and etch in sources.list but preference
points towards etch. It seems apt prints it takes the sid version,
when both are identical.
The typescript of the upgrade is here:
http://www.alzental-castle.de/~rd/upgrade-to-etch/
Summary of issues:
-------------------------
-> aptitude refused the upgrade: No soultion found for the conflicts
open: 11182; closed: 4969; defer: 0; conflict: 3
No solution found within the allotted time. Try harder? [Y/n]
Not sure if aptitude from etch would have done better here. I went with
apt-get for the critical part.
-> during the upgrade apt wanted to remove the running kernel
Wanted to remove the running kernel, but asked before:
Remove the running kernel image (not recommended) [No]?
-> postgres-client upgrade confused apt/dpkg completely. Installation
of all following packages failed
Preparing to replace postgresql-client 7.4.7-6sarge4
(using .../postgresql-client_7.5.22_all.deb) ...
install: `/var/lib/postgres/dumpall/7.4': Not a directory
dpkg: warning - old pre-removal script returned error exit status 1
dpkg - trying script from the new package instead ...
dpkg: error
processing /var/cache/apt/archives/postgresql-client_7.5.22_all.deb
(--unpack):
there is no script in the new version of the package - giving up
dpkg: considering removing postgresql-client in favour of
postgresql-client-common ...
dpkg: yes, will remove postgresql-client in favour of
postgresql-client-common.
Unpacking postgresql-client-common
(from .../postgresql-client-common_71_all.deb) ...
install: `/var/lib/postgres/dumpall/7.4': Not a directory
dpkg: error
processing /var/cache/apt/archives/postgresql-client-common_71_all.deb
(--unpack):
subprocess pre-removal script returned error exit status 1
Unpacking postgresql-client-7.4
(from .../postgresql-client-7.4_1%3a7.4.16-1_i386.deb) ...
install: `/var/lib/postgres/dumpall/7.4': Not a directory
dpkg: error
processing /var/cache/apt/archives/postgresql-client-7.4_1%3a7.4.16-1_i386.deb
(--unpack):
subprocess pre-removal script returned error exit status 1
Preparing to replace powernowd 0.90-3
(using .../powernowd_0.97-1_i386.deb) ...
Stopping powernowd: powernowd.
install: `/var/lib/postgres/dumpall/7.4': Not a directory
Why is powernowd worried about postgres/dumpall/7.4 ???
-> The new kernel was picked up automatically during userspace
upgrade. And install failed. (I think) I fixed that manually later.
Setting up linux-image-2.6.18-4-686 (2.6.18.dfsg.1-11) ...
Hmm. The package shipped with a symbolic
link /lib/modules/2.6.18-4-686/source
However, I can not read the target: No such file or directory
Therefore, I am deleting /lib/modules/2.6.18-4-686/source
Running depmod.
Finding valid ramdisk creators.
Using mkinitrd.yaird to build the ramdisk.
yaird error: command not found: /usr/bin/ldd (fatal)
mkinitrd.yaird failed to create initrd image.
Failed to create initrd image.
dpkg: error processing linux-image-2.6.18-4-686 (--configure):
subprocess post-installation script returned error exit status 9
Certainly there is an /usr/bin/ldd
silverboxy:/etc/cups# ls -l /usr/bin/ldd
-rwxr-xr-x 1 root root 5972 Feb 21 16:13 /usr/bin/ldd
silverboxy:/etc/cups#
-> apt-proxy gets removed during aptitude upgrade. When apt-proxy is
used for the upgrade, the upgrade is broken. So no upgrades with
apt-proxy on localhost are possible with that method.
-> Annoying aptitude cycle towards the end
aptitude dist-upgrade decided to remove a few packages each run
-> bittornado had an upgrade problem
Had to remove btdownloadheadless
silverboxy:~# mv /var/lib/dpkg/alternatives/btdownloadheadless .
(see typescript for details)
What I missed:
--------------
- create a repair CD *before* upgrading (at least for the
ones which want to be on the save side).
- update iceweasel early to have a working browser in case something goes
wrong
-> everything went fine, so no problem not having this stuff.
--
Rainer Dorsch
Lärchenstr. 6
D-72135 Dettenhausen
07032-359190
email: rdorsch@web.de
jabber: rdorsch@jabber.org
GPG Fingerprint: 5966 C54C 2B3C 42CC 1F4F 8F59 E3A8 C538 7519 141E
Full GPG key: http://pgp.mit.edu/
Reply to: