Package: debootstrap Version: 1.0.56 Severity: normal If using debootstrap to create a debian or ubuntu rootfs on a non-debian system, the baked-in assumption that MAKEDEV is in /sbin is wrong. (It's not true on an OE rootfs, for example).
The instructions in README for creating such a rootfs say: Unpack the tarball then: make devices.tar.gz export DEBOOTSTRAP_DIR=`pwd` debootstrap sid sid The make devices.tar.gz step fails when MAKEDEV is not in /sbin. We could stop using MAKEDEV, as suggested in #571136. In the meantime, changing the line in Makefile MAKEDEV := /sbin/MAKEDEV to MAKEDEV ?= /sbin/MAKEDEV would allow make to be called with a setting for where MAKEDEV is (copying a version over from somewhere should be practical) make MAKEDEV='/home/user/utils/MAKEDEV' devices.tar.gz I tested this and it work (so long as an absolute path is given) -- System Information: Debian Release: 7.3 APT prefers stable APT policy: (990, 'stable') Architecture: i386 (i686) Kernel: Linux 3.2.0-kvm-i386-20110111 (SMP w/1 CPU core) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
