Bug#817236: schroot: no access to pseudo-terminals in new chroots
Package: debootstrap
Version: 1.0.87
Followup-For: Bug #817236
(Not CCing people on purpose because this doesn't add to the current thread's
discussion:)
Just wanted to add for the record (e.g. online readers) that Ansgar's
workaround of replacing the current fstab /dev/pts line does works to unbreak
errors like "out of pty devices".
However, it breaks other things like su, which requires to be run from a
terminal but now can't access the host's terminal via /dev/pts. This breakage
itself can be worked around by running su inside `script /dev/null`, but this
might not work for everything.
Anyway, the original workaround solves my immediate problem of python tests
failing.
X
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (300, 'unstable'), (200, 'experimental'), (1, 'experimental-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.8.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages debootstrap depends on:
ii wget 1.18-4
Versions of packages debootstrap recommends:
ii debian-archive-keyring 2014.3
ii gnupg 2.1.16-2
debootstrap suggests no packages.
-- no debconf information
Reply to: