Your message dated Sun, 30 Sep 2007 21:47:11 +0000 with message-id <[EMAIL PROTECTED]> and subject line Bug#324446: fixed in lilo-installer 1.24 has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message ---Package: debian-installer Severity: important Justification: prevents installation with LILO When installing SID with a recent installer nightly, LILO failed to install: Setting up lilo (22.6.1-6.2) ... mount: /dev/hda1 already mounted or /boot busy dpkg: error processing lilo (--configure): subprocess post-installation script returned error exit status 32 Errors were encountered while processing: lilo E: Sub-process /usr/bin/dpkg returned an error code (1) My partition scheme is as follows: hda1 primary ext2 /boot 41.13 MB hda2 primary ReiserFS / 15002.92 MB hda3 primary ReiserFS /home 23960.25 hda4 primary swap 1003.49 (Yeah, I'm sure that my partitioning scheme is poorly thought out.) I'll mention another problem for which I will not open a separate report as I believe that it is another facet of the fundamental problem: To fix this problem, I umounted /boot, chrooted to /target, mounted /boot, and tried again (if I am correctly remembering the order of events), this time getting a different error: 'Fatal: open /vmlinuz: No such file or directory'. I had to re-install (with dpkg) the kernel and try again before it finally worked. I am guessing that this is because the installer had installed the kernel to the /boot directory on the / partition rather than the /boot partition (in fact, I see it there now when I don't mount /boot). I suspect that this is important because it means that /target/boot needs to be mounted not only for the installation of LILO, but also for the installation of the kernel, if I understand correctly. I still have my installation logs if you need more from them. Much love, -- Miciah Masters <[EMAIL PROTECTED]> / <[EMAIL PROTECTED]>
--- End Message ---
--- Begin Message ---Source: lilo-installer Source-Version: 1.24 We believe that the bug you reported is fixed in the latest version of lilo-installer, which is due to be installed in the Debian FTP archive: lilo-installer_1.24.dsc to pool/main/l/lilo-installer/lilo-installer_1.24.dsc lilo-installer_1.24.tar.gz to pool/main/l/lilo-installer/lilo-installer_1.24.tar.gz lilo-installer_1.24_amd64.udeb to pool/main/l/lilo-installer/lilo-installer_1.24_amd64.udeb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jérémy Bobbio <[EMAIL PROTECTED]> (supplier of updated lilo-installer package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.7 Date: Sun, 30 Sep 2007 23:33:03 +0200 Source: lilo-installer Binary: lilo-installer Architecture: source amd64 Version: 1.24 Distribution: unstable Urgency: low Maintainer: Debian Install System Team <[EMAIL PROTECTED]> Changed-By: Jérémy Bobbio <[EMAIL PROTECTED]> Description: lilo-installer - Install LILO on a hard disk (udeb) Closes: 294881 322037 324446 341380 432314 441016 Changes: lilo-installer (1.24) unstable; urgency=low . [ Jérémy Bobbio ] * Use link_in_boot to create image paths in lilo.conf. (Closes: #341380, #294881) * Reuse update_mtab from grub-installer. (Closes: #324446, #322037) * Fix serial console setup if there are command-line parameters after "console=". * Fix lilo-installer/serial-console wrong port speed substition if no port speed was specified on the command-line. * Remove obsolete devfs-style device names from lilo-installer/manual_bootdev. (Closes: #441016) * Clean-up devfs-style device names. (Closes: #432314) . [ Updated translations ] * Bengali (bn.po) by Jamil Ahmed * French (fr.po) by Christian Perrier * Italian (it.po) by Stefano Canepa * Dutch (nl.po) by Frans Pop * Panjabi (pa.po) by A S Alam * Portuguese (Brazil) (pt_BR.po) by Felipe Augusto van de Wiel (faw) * Russian (ru.po) by Yuri Kozlov * Vietnamese (vi.po) by Clytie Siddall Files: 65e6e7161453191ecaa2d86a0d96a37c 678 debian-installer standard lilo-installer_1.24.dsc bdb343f0d5370b50f8444e62e875913d 92867 debian-installer standard lilo-installer_1.24.tar.gz 30f11644c505222ee576685fb6fbc788 62300 debian-installer standard lilo-installer_1.24_amd64.udeb Package-Type: udeb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHABcq2PUjs9fQ72URArxJAJ9PWgaC7Ev+8Sh3AJFwBodsQ3oXRgCfdW1k 5Uiw64YJaoGVwfr+BC/MaV0= =Y3Wp -----END PGP SIGNATURE-----
--- End Message ---
