Package: autopkgtest Version: 2.3.8 Severity: wishlist Adding user's login to root-users configuration of schroot allows autopkgtest to invoke apt-get with necessary privileges, but then tests also run under root user, instead of the original user, which is undesirable for a few reasons:
> yoh 15703 0.4 \_ /usr/bin/python /usr/bin/adt-run --no-built-binaries > ./ --- adt-virt-schroot sid-i386 > yoh 15704 0.3 \_ /usr/bin/python /usr/bin/adt-virt-schroot > sid-i386 > root 17058 0.3 \_ schroot -r -d / -c > sid-i386-5094c780-f425-4543-a3f6-9145051d9161 -u root -- sh -c set -e; exec > 0<'/dev/null' 1>'/tmp/adt-run.3J1ybG/tree0t-unittests-stdout' > 2>'/tmp/adt-run.3J1ybG/tree0t-unittests-stderr'; cd '/tmp/adt-r > root 17059 0.0 \_ su -c > /tmp/adt-run.3J1ybG/tree0-tree/debian/tests/unittests > root 17060 0.0 \_ /bin/sh > /tmp/adt-run.3J1ybG/tree0-tree/debian/tests/unittests > root 17062 88.2 \_ /usr/bin/python2.7 > /usr/bin/nosetests-2.7 patsy it would be nice if schroot first initiated the session, used root for apt-get calls, and then actual tests call under a normal original user. Even better (although probably worth a separate wishlist bug?) would be if it allowed execution under another (specified, or temporarily created within the chroot) user thus to eliminate effects of local (existing) user configuration. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages autopkgtest depends on: ii apt-utils 0.9.8.2 ii debhelper 9.20130630 ii pbuilder 0.215 ii python 2.7.5-5 ii python-debian 0.1.21+nmu2 autopkgtest recommends no packages. Versions of packages autopkgtest suggests: pn autopkgtest-xenlvm <none> ii curl 7.32.0-1 -- debconf-show failed -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
