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

Bug#472389: marked as done (busybox: no longer falles back to busybox applets if no executable if found)



Your message dated Mon, 24 Mar 2008 09:02:07 +0000
with message-id <E1JdiZD-0003Ad-2r@ries.debian.org>
and subject line Bug#472389: fixed in busybox 1:1.9.2-1
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 owner@bugs.debian.org
immediately.)


-- 
472389: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=472389
Debian Bug Tracking System
Contact owner@bugs.debian.org 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 information

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---
--- Begin Message ---
Source: busybox
Source-Version: 1:1.9.2-1

We believe that the bug you reported is fixed in the latest version of
busybox, which is due to be installed in the Debian FTP archive:

busybox-static_1.9.2-1_amd64.deb
  to pool/main/b/busybox/busybox-static_1.9.2-1_amd64.deb
busybox-udeb_1.9.2-1_amd64.udeb
  to pool/main/b/busybox/busybox-udeb_1.9.2-1_amd64.udeb
busybox_1.9.2-1.diff.gz
  to pool/main/b/busybox/busybox_1.9.2-1.diff.gz
busybox_1.9.2-1.dsc
  to pool/main/b/busybox/busybox_1.9.2-1.dsc
busybox_1.9.2-1_amd64.deb
  to pool/main/b/busybox/busybox_1.9.2-1_amd64.deb
busybox_1.9.2.orig.tar.gz
  to pool/main/b/busybox/busybox_1.9.2.orig.tar.gz



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 472389@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bastian Blank <waldi@debian.org> (supplier of updated busybox 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 ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Mon, 24 Mar 2008 09:40:13 +0100
Source: busybox
Binary: busybox busybox-static busybox-udeb
Architecture: source amd64
Version: 1:1.9.2-1
Distribution: unstable
Urgency: low
Maintainer: Debian Install System Team <debian-boot@lists.debian.org>
Changed-By: Bastian Blank <waldi@debian.org>
Description: 
 busybox    - Tiny utilities for small and embedded systems
 busybox-static - Standalone rescue shell with tons of builtin utilities
 busybox-udeb - Tiny utilities for the debian-installer (udeb)
Closes: 472389
Changes: 
 busybox (1:1.9.2-1) unstable; urgency=low
 .
   * New upstream release.
   * [deb] Reenable prefer applets.
   * [deb, static] Make the shell use applets first. (closes: #472389)
Files: 
 5d64b130c59da9ea3a44302ec2ae4c72 674 - optional busybox_1.9.2-1.dsc
 eec10c0bd223729c6dc363c600bf2d09 2118529 - optional busybox_1.9.2.orig.tar.gz
 c07c0cc710bf2984b7cea1aebf7a7b17 18732 - optional busybox_1.9.2-1.diff.gz
 dd761c4968605aeb9693f88ef81156bd 323622 utils optional busybox_1.9.2-1_amd64.deb
 17ed7722def51a15b97e874a4792a8cb 931854 shells optional busybox-static_1.9.2-1_amd64.deb
 f7a79f402c0703b0ddd42be7051ff570 135150 debian-installer extra busybox-udeb_1.9.2-1_amd64.udeb
Package-Type: udeb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iEYEARECAAYFAkfnalEACgkQxWtQqFixGB4UfgCfeQt9iC0Emi4i6BTJiUXXQEQX
PIIAnigLlVifP3qvRYz1AJ69xphLKoc+
=vdye
-----END PGP SIGNATURE-----



--- End Message ---

Reply to: