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

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

Bug#855094: initramfs-tools-core: Error on upgrade if cryptsetup is installed, but a current busybox isn't

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

Contents

  Bug#855094: initramfs-tools-core: Error on upgrade if cryptsetup is installed, but a current busybox isn't Jan Echternach <jan@goneko.de> - 2017-02-14 01:30 +0100
    Bug#855094: initramfs-tools-core: Error on upgrade if cryptsetup is installed, but a current busybox isn't intrigeri <intrigeri@debian.org> - 2017-04-02 10:00 +0200
      Bug#855094: [pkg-cryptsetup-devel] Bug#855094: initramfs-tools-core: Error on upgrade if cryptsetup is installed, but a current busybox isn't Guilhem Moulin <guilhem@guilhem.org> - 2017-04-02 10:20 +0200
        Bug#855094: [pkg-cryptsetup-devel] Bug#855094: initramfs-tools-core: Error on upgrade if cryptsetup is installed, but a current busybox isn't intrigeri <intrigeri@debian.org> - 2017-04-02 10:50 +0200
      Bug#855094: initramfs-tools-core: Error on upgrade if cryptsetup is installed, but a current busybox isn't Ben Hutchings <ben@decadent.org.uk> - 2017-04-02 15:40 +0200
        Bug#855094: initramfs-tools-core: Error on upgrade if cryptsetup is installed, but a current busybox isn't Ben Hutchings <ben@decadent.org.uk> - 2017-04-02 16:00 +0200
    Processed: Re: Bug#855094: initramfs-tools-core: Error on upgrade  if cryptsetup is installed, but a current busybox isn't owner@bugs.debian.org (Debian Bug Tracking System) - 2017-04-02 15:40 +0200
    Bug#855094: marked as done (initramfs-tools-core: Error on  upgrade if cryptsetup is installed, but a current busybox isn't) owner@bugs.debian.org (Debian Bug Tracking System) - 2017-04-09 02:10 +0200

#56969 — Bug#855094: initramfs-tools-core: Error on upgrade if cryptsetup is installed, but a current busybox isn't

Package: initramfs-tools-core
Version: 0.127
Severity: serious
Justification: Policy 3.5

I tried a partial upgrade of initramfs-tools, but it failed, complaining that
busybox was too old, see console messages below. The version of busybox
installed at that time was 1:1.22.0-9+deb8u1. I solved this problem by
upgrading busybox to version 1:1.22.0-19+b1.

I investigated this a bit and found that
/usr/share/initramfs-tools/conf-hooks.d/cryptsetup, which belongs to the
cryptsetup package, sets BUSYBOX=Y (both the current stable and testing
versions of cryptsetup do that).

I think this error could also occur on a complete upgrade if busybox is not
installed because neither initramfs-tools nor cryptsetup depends on busybox.


  # apt-get install initramfs-tools{,-core}/unstable
  Reading package lists... Done
  Building dependency tree       
  Reading state information... Done
  Selected version '0.127' (Debian:testing, Debian:unstable [all]) for 'initramfs-tools'
  Selected version '0.127' (Debian:testing, Debian:unstable [all]) for 'initramfs-tools-core'
  [...]
  Preparing to unpack .../klibc-utils_2.0.4-9_i386.deb ...
  Adding 'diversion of /usr/share/initramfs-tools/hooks/klibc to /usr/share/initramfs-tools/hooks/klibc^i-t by klibc-utils'
  Unpacking klibc-utils (2.0.4-9) over (2.0.4-2) ...
  Preparing to unpack .../libklibc_2.0.4-9_i386.deb ...
  Unpacking libklibc (2.0.4-9) over (2.0.4-2) ...
  Preparing to unpack .../initramfs-tools_0.127_all.deb ...
  '/etc/initramfs-tools/initramfs.conf' -> '/etc/initramfs-tools/initramfs.conf.dpkg-remove'
  Unpacking initramfs-tools (0.127) over (0.120+deb8u2) ...
  dpkg: warning: unable to delete old directory '/var/lib/initramfs-tools': Directory not empty
  Selecting previously unselected package initramfs-tools-core.
  Preparing to unpack .../initramfs-tools-core_0.127_all.deb ...
  Unpacking initramfs-tools-core (0.127) ...
  Setting up libklibc (2.0.4-9) ...
  Processing triggers for man-db (2.7.0.2-5) ...
  Setting up klibc-utils (2.0.4-9) ...
  Setting up initramfs-tools-core (0.127) ...
  removed '/etc/initramfs-tools/initramfs.conf.dpkg-remove'
  Setting up initramfs-tools (0.127) ...
  Installing new version of config file /etc/kernel/postinst.d/initramfs-tools ...
  update-initramfs: deferring update (trigger activated)
  Removing obsolete conffile /etc/bash_completion.d/initramfs-tools ...
  Processing triggers for initramfs-tools (0.127) ...
  update-initramfs: Generating /boot/initrd.img-3.16.0-4-amd64
  E: busybox or busybox-static, version 1:1.22.0-17~ or later, is required but not installed
  update-initramfs: failed for /boot/initrd.img-3.16.0-4-amd64 with 1.
  dpkg: error processing package initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   initramfs-tools
  E: Sub-process /usr/bin/dpkg returned an error code (1)


-- System Information:
Debian Release: 8.7
  APT prefers stable
  APT policy: (813, 'stable'), (812, 'oldstable'), (600, 'unstable-debug'), (600, 'unstable'), (550, 'testing-debug'), (550, 'testing'), (510, 'experimental-debug'), (510, 'experimental')
Architecture: i386 (x86_64)
Foreign Architectures: amd64

Kernel: Linux 4.9.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages initramfs-tools-core depends on:
ii  cpio               2.11+dfsg-4.1+deb8u1
ii  klibc-utils        2.0.4-9
ii  kmod               18-3
ii  module-init-tools  18-3
ii  udev               215-17+deb8u6

Versions of packages initramfs-tools-core recommends:
ii  busybox  1:1.22.0-19+b1

Versions of packages initramfs-tools-core suggests:
pn  bash-completion  <none>

-- no debconf information

[toc] | [next] | [standalone]

#57411

Hi initramfs-tools & cryptsetup maintainers,

initramfs-tools-core has:

  Recommends: busybox (>= 1:1.22.0-17~) | busybox-static (>= 1:1.22.0-17~)

… which makes sense since initramfs-tools itself can work
without busybox.

But then indeed, the cryptsetup hook requires busybox. Still,
cryptsetup can be useful in some cases without busybox being
installed, so it has:

  Recommends: busybox | busybox-static

So all the dependencies seem technically correct to me, it's "just"
that the resulting user experience is poor.

I see no obvious perfect solution. The options I can think of are:

1. Keeping things as-is:
   - Affected systems: partial upgrades, systems where Recommends were
     manually disabled; I don't think that full upgrades from Jessie
     to Stretch are affected, since the initramfs is updated via
     a dpkg trigger, after all packages have been upgraded.
     In other words, only advanced users are affected.
   - Impact: initramfs is not generated, and APT/dpkg exit with an
     error message that tells the user what the problem is, and
     suggests how to fix it.

2. Making initramfs-tools-core depend on a new enough busybox: pulls
   busybox (installed size 746 kB, no dependencies besides libc6) even
   on systems that don't need it, i.e. those that haven't cryptsetup
   installed, and haven't busybox already pulled by anything else.

3. Making cryptsetup depend on a new enough busybox: pulls busybox
   (installed size 746 kB, no dependencies besides libc6) even on
   systems that don't need it; this growth impacts only systems with
   Recommends disabled (otherwise they would already have busybox
   installed) and systems that use another initramfs generator that
   doesn't require busybox, such as dracut.

IMO option 3 is better than option 2:

 * option 3 makes things worse than options 1 and 2 only in rarer cases
 * busybox has greater chances to be needed when cryptsetup is
   installed than when it's not
 * initramfs-tools-core is installed even on relatively minimal
   systems, while cryptsetup might not be

So at this point, I suggest this bug is reassigned to cryptsetup, and
option 3 is implemented there. But downgrading to non-RC and leaving
things as-is seems acceptable to me as well.

Thoughts?

Cheers,
-- 
intrigeri

[toc] | [prev] | [next] | [standalone]

#57412 — Bug#855094: [pkg-cryptsetup-devel] Bug#855094: initramfs-tools-core: Error on upgrade if cryptsetup is installed, but a current busybox isn't

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

Hi intrigeri,

On Sun, 02 Apr 2017 at 09:50:55 +0200, intrigeri wrote:
> So at this point, I suggest this bug is reassigned to cryptsetup, and
> option 3 is implemented there. But downgrading to non-RC and leaving
> things as-is seems acceptable to me as well.
> 
> Thoughts?

I think the proper fix would be to split cryptsetup's initramfs bits to
a separate package (depending on busybox), cf. #783297.  It's
unfortunate that we didn't implement that in time for Stretch, but
considering the impact of this, I'd favor downgrading the severity and
merging the bugs for the time being.

Cheers,
-- 
Guilhem.

[toc] | [prev] | [next] | [standalone]

#57414 — Bug#855094: [pkg-cryptsetup-devel] Bug#855094: initramfs-tools-core: Error on upgrade if cryptsetup is installed, but a current busybox isn't

Guilhem Moulin:
> I think the proper fix would be to split cryptsetup's initramfs bits to
> a separate package (depending on busybox), cf. #783297.  It's
> unfortunate that we didn't implement that in time for Stretch, but
> considering the impact of this, I'd favor downgrading the severity and
> merging the bugs for the time being.

Makes sense to me!

Cheers,
-- 
intrigeri

[toc] | [prev] | [next] | [standalone]

#57419

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

Control: tag -1 pending

On Sun, 2017-04-02 at 09:50 +0200, intrigeri wrote:
[...]
> I see no obvious perfect solution. The options I can think of are:
>
> 1. Keeping things as-is:
>    - Affected systems: partial upgrades, systems where Recommends were
>      manually disabled; I don't think that full upgrades from Jessie
>      to Stretch are affected, since the initramfs is updated via
>      a dpkg trigger, after all packages have been upgraded.
>      In other words, only advanced users are affected.
>    - Impact: initramfs is not generated, and APT/dpkg exit with an
>      error message that tells the user what the problem is, and
>      suggests how to fix it.
> 
> 2. Making initramfs-tools-core depend on a new enough busybox: pulls
>    busybox (installed size 746 kB, no dependencies besides libc6) even
>    on systems that don't need it, i.e. those that haven't cryptsetup
>    installed, and haven't busybox already pulled by anything else.
[...]

How about "Breaks: busybox (<< 1:1.22.0-17~)"?  I think that does the
job.  I've actually committed that change but failed to upload yet.

Ben.

-- 
Ben Hutchings
It is impossible to make anything foolproof because fools are so
ingenious.

[toc] | [prev] | [next] | [standalone]

#57421

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

On Sun, 2017-04-02 at 15:42 +0200, intrigeri wrote:
> Hi,
> 
> Ben Hutchings:
> > How about "Breaks: busybox (<< 1:1.22.0-17~)"?  I think that does the
> > job.

(I actually include busybox-static in the Breaks field too.)

> Yes :) At least it'll ensure that busybox, if installed, is the right
> one (which is probably the best we can do as far as initramfs-tools is
> concerned). Thanks!
> 
> It won't ensure that busybox is installed when the cryptsetup hook
> needs it though. But that's another problem, and as Guilhem pointed
> out it's well tracked elsewhere already.

Correct, but the installer ensures that that happens.

Ben.

-- 
Ben Hutchings
It is impossible to make anything foolproof because fools are so
ingenious.

[toc] | [prev] | [next] | [standalone]

#57418 — Processed: Re: Bug#855094: initramfs-tools-core: Error on upgrade if cryptsetup is installed, but a current busybox isn't

Processing control commands:

> tag -1 pending
Bug #855094 [initramfs-tools-core] initramfs-tools-core: Error on upgrade if cryptsetup is installed, but a current busybox isn't
Added tag(s) pending.

-- 
855094: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855094
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#57488 — Bug#855094: marked as done (initramfs-tools-core: Error on upgrade if cryptsetup is installed, but a current busybox isn't)

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

Your message dated Sun, 09 Apr 2017 00:04:16 +0000
with message-id <E1cx0L2-000D3v-9A@fasolo.debian.org>
and subject line Bug#855094: fixed in initramfs-tools 0.128
has caused the Debian Bug report #855094,
regarding initramfs-tools-core: Error on upgrade if cryptsetup is installed, but a current busybox isn't
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.)


-- 
855094: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855094
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

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

csiph-web