[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#351488: marked as done (initramfs-tools 0.46 with linux-image-2.6.15-1-686)

Your message dated Sun, 29 Jul 2007 02:34:47 +0200
with message-id <20070729003447.GJ31608@stro.at>
and subject line initramfs-tools 0.46 with linux-image-2.6.15-1-686
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: linux-image-2.6.15-1-686
Version: 2.6.15-4

When installing linux-image-2.6.15-1-686 with the initramfs-tools from
testing, during the initramfs generation I got the following messages:

...
Setting up linux-image-2.6.15-1-686 (2.6.15-4) ...
Running depmod.
Finding valid ramdisk creators.
Using mkinitramfs to build the ramdisk.
rm: cannot remove `/tmp/mkinitramfs_m4tdQ2/bin/sh': No such file or directory
cpio: ./lib/klibc-*.so: No such file or directory
...

Said initramfs image didn't work on reboot, I didn't really expect it to.

Upon upgrading to initramfs-tools 0.51 the problem was fixed.
I'd recommend changing linux-image-2.6.15-* dependency of
initramfs-tools to initramfs-tools (>=0.51), I do not know if
yaird/linux-initramfs-tool has simular problems...

Be well,
Tristan

--- End Message ---
--- Begin Message --- 
Version: 2.6.18-1

Depends: module-init-tools (>= 0.9.13), coreutils (>= 5.96), initramfs-tools (>= 0.55) | yaird (>= 0.0.12-8) | linux-initramfs-tool

your request of higher dep than 0.51 had been handled inbetween,
thus closing.

-- 
maks

--- End Message ---
Reply to: