Package: initramfs-tools
Version: 0.85b
Severity: normal
When lilo -t fails update-initramfs exits with an error (due to set -e)
but provides no indication to the user. When called in postinst the
failure is reported by, e.g., aptitude but there is no explanation of
what went wrong.
This could leave a system unbootable if update-initramfs is run outside
of package management (where the failure is invisible) or if the user doesn't
realize an upgrade failure might be serious.
I suggest that the stderr of lilo -t should at least be provided to the
user, or perhaps run_lilo() should do set +e and then complain loudly if
lilo -t fails.
-- Package-specific info:
-- /proc/cmdline
auto BOOT_IMAGE=Linux ro root=fd00
-- /proc/filesystems
cramfs
ext3
-- lsmod
[ Snip. Not relavent to this bug. ]
-- kernel-img.conf
do_symlinks = yes
relative_links = yes
do_bootloader = no
do_bootfloppy = no
do_initrd = yes
link_in_boot = no
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-2-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages initramfs-tools depends on:
ii busybox 1:1.1.3-3 Tiny utilities for small and embed
ii cpio 2.6-17 GNU cpio -- a program to manage ar
ii klibc-utils 1.4.30-1 small statically-linked utilities
ii module-init-tools 3.3-pre3-1 tools for managing Linux kernel mo
pn udev <none> (actually this is installed
but has failed at the moment due
to lilo being broken)
initramfs-tools recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
