On Sun, 2016-02-28 at 14:28 +0100, Reto Schoch wrote:
> On Sun, 28 Feb 2016 12:41:03 +0000 Ben Hutchings <ben@decadent.org.uk>
> wrote:
> > On Sun, 2016-02-28 at 12:47 +0100, Christophe wrote:
> > > ----- Ben Hutchings <ben@decadent.org.uk> a écrit :
> > > >
> > > > On Sat, 2016-02-27 at 13:04 +0100, Christophe wrote:
> > > > > Package: initramfs-tools
> > > > > Version: 0.123
> > > > > Severity: important
> > > > >
> > > > > [...]
> > > > >
> > > > > Let me know if there is some info you'd need to debug the issue.
> > > >
> > > > I wonder if busybox got upgraded too late. Â Is this reproducible if
> you
> > > > run 'update-initramfs -u' now?
> > > >
> > > > Ben.
> > >
> > > Hi Ben,
> > >
> > > Unfortunately running this command still gives me the error.
> > > Out of curiosity I have started some investigations, and the message
> comes from the script "mkinitramfs" from this check:
> > >
> > > if [ "${BUSYBOX}" = "y" ] && [ -z "${BUSYBOXDIR}" ]; then
> > >
> > > I have seen this:
> > > Â - BUSYBOX is properly set to "y" from
> /etc/initramfs-tools/initramfs.conf
> > > Â - BUSYBOXDIR, however, is prepared empty at the beginning of
> mkinitramfs, but never given a value afterwards... Any idea how it is
> supposed to be defined?
> >
> > It's done by /usr/share/initramfs-tools/conf-hooks.d/busybox, which is
> > installed by busybox. Â Does that file exist?
> >
> > You originally said:
> >
> > > This is strange because I seem to have this:
> > > Â busybox => 1:1.22.0-18
> > > Â busybox-static => 1:1.22.0-18
> >
> > That's impossible because these packages conflict with each other.
> >
> > What does "debsums busybox busybox-static" report? Â (You might need to
> > install the debsums package.)
> >
> > Ben.
> >
> > --
> > Ben Hutchings
> > Knowledge is power. France is bacon.
>
> Hi Ben
>
> I have the same error message. Running 'update-initramfs -u' gives the
> following error message:
>
> update-initramfs: Generating /boot/initrd.img-4.3.0-1-686-pae
> 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-4.3.0-1-686-pae with 1.
>
> It looks like the new version of initramfs-tools treats busybox as
> "depends" while it should only be "recommends".
>
> Can you confirm?
>>This is explained in the NEWS file.
Ok, I didn't see that one:
* If initramfs-tools is configured to use busybox but it is not
installed, mkinitramfs will now fail. Previously it would quietly use
klibc instead, sometimes producing a broken initramfs. You may need
to modify /etc/initramfs-tools/initramfs.conf or install busybox when
upgrading.
So I changed initramfs.conf to "BUSYBOX=n", rebooted and ran run 'update-initramfs -u' and there ist no error message anymore.
Thus I presume that this is also for Christophe in fact not a bug but a handling error.
Reto.