[Yaird-devel] Bug#350880: failure to create ramfs does not abort configuration of kernel image

[martin f krafft]

Package: yaird
Version: 0.0.12-3
Severity: important

If I configure a kernel image, using yaird for the initrd, and /boot
runs full, the kernel is still configured:

  cirrus:~# dpkg-reconfigure linux-image-2.6.15-1-k7
  Running depmod.
  Finding valid ramdisk creators.
  Using mkinitrd.yaird to build the ramdisk.
  yaird error: Could not copy /lib/tls/libc-2.3.5.so to /boot/initrd.img-2.6.15-1-k7.new.7behkOlAU1rVENze/lib/tls/libc-2.3.5.so (fatal)
  mkinitrd.yaird failed to create initrd image.
  Failed to create initrd image.
  cirrus:~# dpkg -l linux-image-2.6.15-1-k7 | grep \^ii
  ii  linux-image-2.6.15-1-k7 2.6.15-3       Linux kernel 2.6.15 image on AMD K7 machines

This results in a kernel panic on next boot ("ran out of compressed
data"). mkinitrd used to handle this situation correctly, leaving
the kernel image package in an unconfigured state.

-- 
 .''`.     martin f. krafft <madduck at debian.org>
: :'  :    proud Debian developer and author: http://debiansystem.info
`. `'`
  `-  Debian - when you have better things to do than fixing a system
 
Invalid/expired PGP (sub)keys? Use subkeys.pgp.net as keyserver!
 
"funny how just when you think life can't possibly get any worse
 it suddenly does."
                                                           -- marvin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature (GPG/PGP)
Url : http://lists.alioth.debian.org/pipermail/yaird-devel/attachments/20060201/f88d7ae4/attachment.pgp