Processing control commands:
> unmerge -1
Bug #841935 [debootstrap] pbuilder: incorrect permissions on /dev/ptmx breaks
openpty()
Bug #817236 [debootstrap] schroot: no access to pseudo-terminals in new chroots
Bug #849168 [debootstrap] pbuilder: Expect programe reported "no more ptys" and
failed
Control: unmerge -1
Control: severity -1 normal
Control: reassign -1 pbuilder
I'm decoupling this bug from debootstrap and making it non-RC because I
suspect the best long-term solution might be to solve it in pbuilder
*and* debootstrap, and debootstrap already has a RC bug representing
the need f
Thorsten Glaser writes:
> … whereas all “new” chroots look like…
>
> ls: cannot access 'base.cow-xenial-amd64/dev/pts/ptmx': No such file or
> directory
> lrwxrwxrwx 1 root root 8 Mai 10 14:10 base.cow-xenial-amd64/dev/ptmx ->
> pts/ptmx
>
> … so I assume that something in debootstrap changed so
@debootstrap maintainers, look near the end for a tl;dr
James Clarke dixit:
>> # ls -l /dev/ptmx
>> lrwxrwxrwx 1 root root 8 Oct 4 06:43 /dev/ptmx -> pts/ptmx
>> # ls -l /dev/pts/ptmx
>> c- 1 root root 5, 2 Oct 24 14:46 /dev/pts/ptmx
>> For comparison this is from my regular system:
>>
4 matches
Mail list logo