Package: sbuild Version: 0.73.0-4 I am trying to do a strange thing: use sbuild with adt-virt-null, without being root. I have discovered that sbuild insists on trying to create /build even if an alternative --build-path is specified:
+ BUILD_PATH=/home/ian/things/Dgit/dgit/tests/tmp/sbuild-adt-null/sbuild-build-path + sbuild --chroot-mode=autopkgtest --autopkgtest-virt-server=/usr/bin/fakeroot --autopkgtest-virt-server-opt=adt-virt-null -D --build-path=/home/ian/things/Dgit/dgit/tests/tmp/sbuild-adt-null/sbuild-build-path '--dpkg-source-opts=-Zgzip -z1 --format=1.0 -sn' ... I: env sh -c cd / && exec "$@" exec /bin/sh -c set -e; if [ ! -d /build ] ; then mkdir -m 0775 /build; fi D: Setting Log Stream Error=1 D: Running command: env sh -c cd / && exec "$@" exec /bin/sh -c set -e; if [ ! -d /build ] ; then mkdir -m 0775 /build; fi mkdir: cannot create directory '/build': Permission denied E: Failed to create build directory /build Failed to set up chroot (I expect that when I get past this I will have to prevent it from running apt.) Full repro: $ git clone git://git.chiark.greenend.org.uk/~ianmdlvl/dgit.git $ cd dgit $ git checkout 904c4128a89555d5caecb100943da23fffd7ee98 $ tests/using-intree tests/tests/sbuild-adt-null 2>&1 |tee ../log You will find that this hangs. That is due to a bug in adt-virt-null, #868576. However, you can look at the logfile; ^Z $ less tests/tmp/sbuild-adt-null/example_1.1-1_amd64.build Observe in that log the error messages I quote above. The file ../log (from tee) will contain the output from the dgit test machinery, which includes much noise, but I don't think is relevant. Ian. -- Ian Jackson <[email protected]> These opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.
