Bug#601011: debootstrap: Fails without an error when it can't create devices
Package: debootstrap
Version: 1.0.25
Severity: important
When debootstrap can't extract devices.tar.gz for some reason, it exists
with an error code 2, but doesn't say anything as to why it failed.
Following with strace, it appears the one failing is tar, because it can't
extract (mknod) the devices from devices.tar.gz. This happened on my system
because I was trying to debootstrap from within an lxc instance created
with the default template which disabled a whole bunch of devices.
Please at least handle the error and display tar's error message.
A bonus point if you just ignore the error, as the failing devices here were
really not important to the chroot:
dev/full
dev/kmem
dev/loop*
dev/mem
dev/port
dev/ram*
Cheers,
Mike
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages debootstrap depends on:
ii wget 1.12-2.1 retrieves files from the web
Versions of packages debootstrap recommends:
ii gnupg 1.4.10-4 GNU privacy guard - a free PGP rep
debootstrap suggests no packages.
-- no debconf information
Reply to: