[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#826709: debootstrap: fail early when debootstrapping foreign arches whose binaries cannot be run

Package: debootstrap
Version: 1.0.81
Severity: wishlist
X-Debbugs-CC: maker@python.it

On #debian-mentors we had a person (CCed) who was trying to create an
armhf chroot like this:

  $ sudo debootstrap --arch=armhf testing /mnt

This failed with this non-intuitive reason:

  W: Failure trying to run: chroot /mnt mount -t proc proc /proc
  W: See /mnt/debootstrap/debootstrap.log for details
  $ cat /mnt/debootstrap/debootstrap.log 
  chroot: failed to run command 'mount': No such file or directory

It would be great if debootstrap would fail early with a message like this:

  This machine cannot run binaries for architecture armhf
  There are two options to work around this:

  Use qemu-debootstrap instead of debootstrap

  Use debootstrap --foreign here and
  use debootstrap --second-stage on armhf

A tool for determining which arches can be run on the current system:

  $ arch-test

When arch-test is not installed, debootstrap could consult a hardcoded
list of typically compatible architectures.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.6.0-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages debootstrap depends on:
ii  wget  1.17.1-2

Versions of packages debootstrap recommends:
ii  debian-archive-keyring  2014.3
ii  gnupg                   1.4.20-6

debootstrap suggests no packages.

-- no debconf information



Attachment: signature.asc
Description: This is a digitally signed message part

Reply to: