On 6 Mar 2017, at 16:40, Simon McVittie wrote:
> On Mon, 06 Mar 2017 at 15:30:04 +, Thorsten Glaser wrote:
>> Simon McVittie dixit:
>>> I'm surprised by this. I would have expected that interactive use of
>>> tty things inside pbuilder would have started failing when you upgraded
>>> to a v4.7
On Mon, 06 Mar 2017 at 15:30:04 +, Thorsten Glaser wrote:
> Simon McVittie dixit:
> >I'm surprised by this. I would have expected that interactive use of
> >tty things inside pbuilder would have started failing when you upgraded
> >to a v4.7+ kernel, because the /dev/pts inside the chroot would
Simon McVittie dixit:
>If you do a `pbuilder login` (or use your failing-build hook) and run
>tty(1) at the resulting prompt, what do you get?
(pbuild5766)root@tglase:/# tty
not a tty
>I'm surprised by this. I would have expected that interactive use of
>tty things inside pbuilder would have sta
On Mon, 06 Mar 2017 at 09:32:22 +, Simon McVittie wrote:
> systemd-nspawn creates a pty outside the container, but then bind-mounts
> it onto /dev/console inside the container. Maybe that would be another
> possibility?
This seems to work fine. tty(1) prints "/dev/console", the same as it does
Simon McVittie dixit:
[… long explanations plus this…]
>Perhaps bind-mounting the host's /dev/pts and also the host's /dev/ptmx
>would work? I'll try that.
Thank you for helping working on it.
>On Sun, 05 Mar 2017 at 22:43:53 +, Thorsten Glaser wrote:
>> I’d also be seriously annoyed if my C
On Sun, 05 Mar 2017 at 22:16:29 +, James Clarke wrote:
> if you want to have use newinstance instead to separate the two, the
> problem is that the chroot can't access the controlling TTY any more, since
> it's only in the host's /dev/pts
systemd-nspawn creates a pty outside the container, but
On Sun, 05 Mar 2017 at 22:16:29 +, James Clarke wrote:
> However, [ptmxmode=666] has to be done on the host, since /dev/pts
> is currently (effectively) bind-mounted (by not being a new instance)
Not with 4.7+ (stretch) kernels it isn't[1], so pbuilder already has this
regression in stretch. I
James Clarke dixit:
>the host's /dev/pts. I would love to see newinstance working, but I tried it
>once and couldn't get it to work, especially with "pbuilder login". Someone
I’d also be seriously annoyed if my C hook running a shell if the
build failed would stop working. (On that note, apparent
On 5 Mar 2017, at 19:53, Simon McVittie wrote:
>
> 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* debootst
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:
>>
On 06.11.2016 23:41, James Clarke wrote:
On 6 Nov 2016, at 20:34, Yuriy M. Kaminskiy wrote:
Andreas Henriksson writes:
It seems /dev/ptmx has incorrect permissions in a pbuilder chroot:
# ls -l /dev/ptmx
lrwxrwxrwx 1 root root 8 Oct 4 06:43 /dev/ptmx -> pts/ptmx
# ls -l /dev/pts/ptmx
c
> On 6 Nov 2016, at 20:34, Yuriy M. Kaminskiy wrote:
>
> Andreas Henriksson writes:
>
>> It seems /dev/ptmx has incorrect permissions in a pbuilder chroot:
>>
>> # 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
Andreas Henriksson writes:
It seems /dev/ptmx has incorrect permissions in a pbuilder chroot:
# 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
Please compare to what's stated in
https://w
Package: pbuilder
Version: 0.226.1
Severity: normal
Tags: patch
Dear Maintainer,
It seems /dev/ptmx has incorrect permissions in a pbuilder chroot:
# 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/pt
16 matches
Mail list logo