Your message dated Wed, 26 Mar 2008 15:33:06 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#472389: busybox: no longer falls back to busybox applets if no executable if found has caused the Debian Bug report #472389, regarding busybox: no longer falles back to busybox applets if no executable if found 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 472389: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=472389 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems
--- Begin Message ---Package: busybox Version: 1:1.9.1-3 Severity: important CC'ing initramfs-tools maintainer, as it directly affects hooks into initramfs-tools. BusyBox 1.1.3 implemented a fallback to its own applets in case no executable could be found: BusyBox v1.1.3 (Debian 1:1.1.3-5) Built-in shell (ash) Enter 'help' for a list of built-in commands. ~ $ printf "foo\n" foo ~ $ PATH= ~ $ export PATH ~ $ printf "foo\n" foo while BusyBox 1.9.1 just throws an error BusyBox v1.9.1 (2008-03-22 22:06:19 UTC) built-in shell (ash) Enter 'help' for a list of built-in commands. ~ $ printf "foo\n" foo ~ $ PATH= ~ $ export PATH ~ $ printf "foo\n" ash: printf: not found Even though this behaviour is understandable, it does break hooks into current initramfs-tools making use of functionality neither provided by klibc nor busybox built-ins (but only as applets for busybox), because initramfs-tools doesn't create {hard,sym}links to busybox (#338405). Potentially affected packages (not checked in depths): - bootcd-mkinitramfs (it seems to use grep) - cryptsetup (it does use basename #466240 and seems to use grep) - evms (it seems to use grep) - initramfs-tools (it does use printf and seems to use awk as well) - live-initramfs (it seems to use awk, basename, grep and printf) - loop-aes-utils (it seems to use grep) - ltsp-client-core (it seems to use grep - mdadm (it seems to use grep) - nbd-client (it seems to use grep) - splashy (it seems to use grep) - uswsusp (it seems to use grep) A workaround seems to be enabling CONFIG_FEATURE_PREFER_APPLETS=y CONFIG_FEATURE_SH_STANDALONE=y FEATURE_SH_STANDALONE was enabled in busybox 1.1.3, even though it prefers busybox applets in favour of shipped executables (unless called with full path names), it might be needed until a better long term solution can be found. Regards Stefan Lippers-Hollmann -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.24-2.6.24.3.slh.11-sidux-amd64 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages busybox depends on: ii libc6 2.7-9 GNU C Library: Shared libraries busybox recommends no packages. -- no debconf informationsignature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---Version: 1:1.9.2-2 These bug reports should be fixed with the upload of version 1:1.9.2-2 of busybox earlier today.
--- End Message ---