On Tue, 2015-10-13 at 15:49 +0200, Olliver Schinagl wrote:
Package: flash-kernel
Version: 3.35+deb8u1
Severity: important
Tags: d-i
Dear Maintainer,
when installing flash-kernel on a very basic and minimal system (created with
multistrap) flash-kernel fails to install.
While flash-kernel does seem to work and is installed afterwards this makes
automated installation via multistrap impossible.
My packages from multistrap looks like this, which as you can see is fairly
minimal
packages=f2fs-tools connman wpasupplicant iptables dropbear avahi-daemon
libv4l-0 lsb-invalid-mta ca-certificates mtd-utils busybox apt usbmount udisks2
rsync
I guess adding some dialog dependancy is probably the quickest fix, but I don't
think is the best solution.
root@system-02880482d32a:~# apt-get install flash-kernel
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
flash-kernel
0 upgraded, 1 newly installed, 0 to remove and 25 not upgraded.
Need to get 0 B/34.2 kB of archives.
After this operation, 76.8 kB of additional disk space will be used.
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package flash-kernel.
(Reading database ... 14355 files and directories currently installed.)
Preparing to unpack .../flash-kernel_3.35+deb8u1_armhf.deb ...
Unpacking flash-kernel (3.35+deb8u1) ...
Setting up flash-kernel (3.35+deb8u1) ...
debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based
frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line
76.)
debconf: falling back to frontend: Readline
readlink: invalid option -- 'm'
[...]
I think the problem is that you're using busybox instead of coreutils
(which is essential and therefore doesn't have to be explicitly
depended on).