Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #51958 > unrolled thread

Bug#809204: busybox is required but not installed

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#809204: busybox is required but not installed 積丹尼 Dan Jacobson <jidanni@jidanni.org> - 2015-12-30 03:20 +0100
    Bug#809204: busybox is required but not installed Ben Hutchings <ben@decadent.org.uk> - 2015-12-31 04:40 +0100

#51958 — Bug#809204: busybox is required but not installed

>>>>> "BH" == Ben Hutchings <ben@decadent.org.uk> writes:
>> OK, but you are still going to run into problems if the user has set
>> 
>> # apt-config dump|egrep Rec\|Sugg
>> APT::Install-Recommends "false";
>> APT::Install-Suggests "0";

BH> Users that do that need to accept that they will encounter errors like
BH> this.

OK, but I am sure yours is the very first package to "lower the
barrier" of
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-binarydeps
in that way.

In the past an entire working Debian could be completely installed counting on only
Depends.

Or maybe
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-binarydeps
needs to have some additional explanation about special cases like this?

[toc] | [next] | [standalone]

#51967

[Multipart message — attachments visible in raw view] — view raw

Control: reopen -1
Control: retitle -1 busybox/klibc selection should remain automatic for systems that don't need busybox

On Wed, 2015-12-30 at 10:10 +0800, 積丹尼 Dan Jacobson wrote:
> > > > > > "BH" == Ben Hutchings <ben@decadent.org.uk> writes:
> > > OK, but you are still going to run into problems if the user has set
> > > 
> > > # apt-config dump|egrep Rec\|Sugg
> > > APT::Install-Recommends "false";
> > > APT::Install-Suggests "0";
> 
> BH> Users that do that need to accept that they will encounter errors like
> BH> this.
> 
> OK, but I am sure yours is the very first package to "lower the
> barrier" of
> https://www.debian.org/doc/debian-policy/ch-relationships.html#s-binarydeps
> in that way.
> 
> In the past an entire working Debian could be completely installed counting on only
> Depends.
> 
> Or maybe
> https://www.debian.org/doc/debian-policy/ch-relationships.html#s-binarydeps
> needs to have some additional explanation about special cases like this?

You've convinced me that this isn't a good way to handle the change.

What I intend to do is to add a third option, BUSYBOX=auto, with the
old semantics of BUSYBOX=y, and make that the default.  On upgrade you
may be prompted to resolve conflicts in the configuration file, but
otherwise nothing will break.

In the case that there are configuration hooks that set BUSYBOX=y,
mkinitramfs will still refuse to create a broken initramfs.

Ben.

-- 
Ben Hutchings
All the simple programs have been written, and all the good names taken.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web