5a7ed86fba
Git wants to ensure that you do not read .git owned by other users. But we fetch+build as 'build' user, and run tests as root user. Those tests calculate git topdir using git rev-parse --show-toplevel, which git now fails. Setting safe.directory, seems wrong. Let's just use bash to figure out the top dir. |
||
|---|---|---|
| .. | ||
| chage | ||
| chroot | ||
| chsh | ||
| cktools | ||
| common | ||
| convtools | ||
| cptools | ||
| crypt | ||
| debian | ||
| expiry | ||
| failures | ||
| grouptools | ||
| libsubid | ||
| log | ||
| login | ||
| newgidmap | ||
| newuidmap | ||
| newusers | ||
| passwd | ||
| split_groups | ||
| su | ||
| subids | ||
| usertools | ||
| bug332198-test.exp | ||
| bug334803-test.exp | ||
| cleanup.sh | ||
| coverage.sh | ||
| README | ||
| run_all | ||
| run_all.coverage | ||
| run_some | ||
This testsuite is NOT SECURE: it will temporarily change your passwords file with known passwords. You should run it on a chroot, or on a secured dedicated system. To test a Debian system: $ mkdir sid-chroot $ sudo debootstrap sid sid-chroot/ http://deb.debian.org/debian/ edit or copy a sources.list $ sudo cp /etc/apt/sources.list sid-chroot/etc/apt/ edit or copy a resolv.conf $ sudo cp /etc/resolv.conf sid-chroot/etc/ $ su - root -c "chroot sid-chroot/ /bin/bash" # mount -t proc proc /proc # mount -t devpts devpts /dev/pts # aptitude update # aptitude install expect # cd /dev ; mknod --mode=666 /dev/ptmx c 5 2