Bug#801688: marked as done (flash-kernel fails with readlink: invalid option -- 'm')
Your message dated Wed, 14 Oct 2015 19:38:54 +0100
with message-id <1444847934.18486.12.camel@hellion.org.uk>
and subject line Re: Bug#801688: flash-kernel fails with readlink: invalid option -- 'm'
has caused the Debian Bug report #801688,
regarding flash-kernel fails with readlink: invalid option -- 'm'
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.)
--
801688: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801688
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
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'
BusyBox v1.22.1 (Debian 1:1.22.0-9+deb8u1) multi-call binary.
Usage: readlink [-fnv] FILE
Display the value of a symlink
-f Canonicalize by following all symlinks
-n Don't add newline
-v Verbose
: Unable to determine The new file
dpkg: error processing package flash-kernel (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
flash-kernel
E: Sub-process /usr/bin/dpkg returned an error code (1)
P.S. 3.46~bpo8+1 also suffers the same problem.
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf
Kernel: Linux 4.3.0-rc1+ (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
On Wed, 2015-10-14 at 12:14 +0200, Olliver Schinagl wrote:
> > 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).
> Depends on how you install your system I suspect.
No it doesn't. If coreutils is essential then must be installed on any
non-buggy Debian system.
> I used multistrap with
> a list of packages (which pulls the bare minimal system in, of which
> busybox or core-utils don't appear to be dependancies) and that
> leaves me with a fully working debian system.
Not if coreutils isn't installed it doesn't. By definition.
Either multistrap is buggy or it is not designed to provide you with a
Debian system in the first place. I don't know which.
> I couldn't find where readlink or readline is being called in
> flash-kernel or its scripts
>From the logs it appears to be used by debconf. This is not a bug in
debconf though, as above any package is entitled to assume coreutils is
installed.
> , but for some reason readlink -m is being
> called which may work with the core-utils, but not with busybox.
>
> Having flash-kernel be functional with atleast busybox doesn't seem
> like
> a strange requirement. Flash-kernel is for embedded systems and thus
> having a bare minimal embedded system isn't all out ot the ordinary
> :)
flash-kernel is not for embedded systems, it is for Debian systems.
I'm closing this bug since it is not AFAICT a bug in Debian.
Ian.
--- End Message ---
Reply to: