Bug#751012: [flash-kernel] Flash-kernel should fail with exit 0 under debrootstrap
On Mon, Jun 09, 2014 at 05:54:35PM +0200, Bastien ROUCARIES wrote:
> On Mon, Jun 9, 2014 at 5:21 PM, Karsten Merker <merker@debian.org> wrote:
> > On Mon, Jun 09, 2014 at 03:48:11PM +0000, bastien ROUCARIES wrote:
> >
> >> Package: flash-kernel
> >> Severity: important
> >>
> >> Flash-kernel should detect it run under debrootstrap and fail gracefully/
> >>
> >> Install message:
> >>
> >> Processing triggers for libc-bin (2.18-7) ...
> >> Processing triggers for initramfs-tools (0.115) ...
> >> update-initramfs: Generating /boot/initrd.img-3.14-1-kirkwood
> >> /bin/df: Warning: cannot read table of mounted file systems: No such file or directory
> >> warning: failed to read mtab
> >> ^Cdpkg: error processing package initramfs-tools (--configure):
> >> subprocess installed post-installation script was interrupted
> >> Errors were encountered while processing:
> >> initramfs-tools
> >> E: Sub-process /usr/bin/dpkg returned an error code (1)
> >
> > Hello,
> >
> > I am trying to understand which problem exactly you have
> > encountered, but I am a bit confused: you have filed a bug
> > against flash-kernel but in the log you have provided, it is not
> > flash-kernel that shows an error message, but initramfs-tools. I
> > also cannot see in which context that has happened and how it
> > relates to debootstrap - by default debootstrap does neither
> > install a kernel image nor flash-kernel. From your log, it looks
> > like you have manually interrupted the update-initramfs process,
> > resulting in the error message above:
>
> No I have not interupted.
>
> I have installed te kirkwood kernel and flash-kernel on my chroot.
Hello,
I unfortunately cannot yet reproduce your problem. Due to the
kernel version (3.14-1) I assume that you are debootstrapping
jessie or sid. I have just debootstrapped a sid/armel chroot
that included flash-kernel and linux-image-3.14-1-kirkwood on
a sid/armhf system without problems:
# debootstrap --arch=armel --include=flash-kernel,linux-image-kirkwood sid armel-sid-chroot http://ftp.de.debian.org/debian
I: Retrieving Release
I: Retrieving Release.gpg
I: Checking Release signature
I: Valid Release signature (key id A1BD8E9D78F7FE5C3E65D8AF8B48AD6246925553)
[...]
I: Configuring linux-image-3.14-1-kirkwood...
I: Configuring flash-kernel...
I: Configuring libgnutls-openssl27:armel...
I: Configuring wget...
I: Configuring libcwidget3:armel...
I: Configuring aptitude...
I: Configuring linux-image-kirkwood...
I: Configuring iputils-ping...
I: Configuring tasksel...
I: Configuring tasksel-data...
I: Configuring perl-modules...
I: Configuring perl...
I: Configuring init-system-helpers...
I: Configuring cron...
I: Configuring rsyslog...
I: Configuring logrotate...
I: Configuring libc-bin...
I: Configuring initramfs-tools...
I: Base system installed successfully.
#
Just to be sure: On which kind of hardware (kirkwood or
non-kirkwood system) and in which Debian release (wheezy, jessie
or sid) are you running the debootstrap command and which release
are you bootstrapping with debootstrap (jessie or sid)?
Have you created your chroot like I did above, i.e. with the
"--include" parameter, or have you first run debootstrap without it
and later on manually installed linux-image-3.14-1-kirkwood and
flash-kernel in the already-created chroot?
Please provide a full log of the whole process starting with the
invocation of debootstrap up to the point where flash-kernel runs
but should not.
Regards,
Karsten
--
Gem. Par. 28 Abs. 4 Bundesdatenschutzgesetz widerspreche ich der Nutzung
sowie der Weitergabe meiner personenbezogenen Daten für Zwecke der
Werbung sowie der Markt- oder Meinungsforschung.
Reply to: