Bug#316955: upgrade-reports: system hangs after woody->sarge upgrade
Package: upgrade-reports
Severity: critical
Justification: breaks the whole system
My system would not boot after the woody->sarge upgrade.
I followed the instructions in the Debian Release notes for sarge:
- edit sources.list
deb http://ftp.jp.debian.org/debian/ sarge main non-free contrib
deb http://security.debian.org/ sarge/updates main contrib non-free
- apt-get update
- aptitude install aptitude
- aptitude install doc-base
- aptitude -f --with-recommends dist-upgrade
The only problem until now was that I had to remove festival for the
upgrade to proceed (reported as a separate bug, #316948). The upgrade went
on apparently succesfully, installing and configuring packages as needed.
The release notes only ask to pay attention to the XFree upgrade notes
before rebooting:
/usr/share/doc/xfree86-common/README.Debian-upgrade.gz
I checked it. I did not upgrade kernel. I thought it was safe to reboot.
But the system hang, with "LI" being the only text on screen.
I used a woody bootable CD to check the system. The problem was solved
after I run 'lilo'. However, I understand that is only necessary if
lilo.conf is changed, or a new kernel is installed. Nothing of that happened.
$ ls -l lilo.conf
-rw-r----- 1 root root 4131 2004-02-02 20:04 lilo.conf
Checking the typescript of the upgrade session, I noticed that lilo was
updated:
Preparing to replace lilo 1:22.2-3 (using .../lilo_1%3a22.6.1-6.2_i386.deb)
...
Unpacking replacement lilo ...
Preparing to replace lilo-doc 1:22.2-3 (using
.../lilo-doc_1%3a22.6.1-6.2_all.deb) ...
Unpacking replacement lilo-doc ...
[...]
Setting up lilo (22.6.1-6.2) ...
Setting up lilo-doc (22.6.1-6.2) ...
Naively maybe, I would have expected lilo to have been re-run if necessary
during the upgrade. Maybe a mention of lilo issues in the Release Notes
would have been welcome.
Regards,
Victor
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.4.18-bf2.4
Locale: LANG=es.ISO-8859-1, LC_CTYPE=es.ISO-8859-1 (charmap=ISO-8859-1) (ignored: LC_ALL set to en_US)
Reply to: