Re: Bug#983423: schroot: regression presumably in 1.6.13-4 after fixing #983423
On Tue, 20 Aug 2024 at 01:30:55 +0100, Simon McVittie wrote:
> The reason for the regression is probably that /dev/pts/ptmx on the host
> has permissions 000, making it inaccessible (despite being functionally
> equivalent to /dev/ptmx which is available to everyone).
Yes, it seems to be this. I've reported the regression as #1079124, please
send any further replies regarding this regression to there.
In future it would be more discoverable (and probably also less effort for
the bug reporter) to report regressions as a new bug with an appropriate
severity, rather than as replies to a closed bug whose solution introduced
the regression.
> It would probably be possible to drop the bind-mounting onto
> /dev/ptmx with modern kernels
Yes, it seems OK: see the patch proposed on #1079124 (tested on 4.19.x
and 6.9.x).
On Tue, 20 Aug 2024 at 01:07:55 +0000, Thorsten Glaser wrote:
> The varios MIPS buildds run 4.19 and some even 4.9 kernels
I'm aware of mips64el buildds (and a porterbox) still running 4.19
(Debian 10 kernel), and I've reminded #1050872 that this continues to be
a cause for concern.
I was not aware of any mips* buildds still on 4.9 (Debian 9 kernel). The
only mips family architecture listed on buildd.debian.org is mips64el, for
which I've been able to confirm that every machine listed on db.debian.org
has at least a Debian 10 kernel, or at least had one in the past and was
working well enough at the time to be able to build and upload some packages.
If there are unofficial mips* buildds outside the buildd.debian.org
infrastructure, then I would hope that either they can be upgraded to a
Debian 10 or later kernel, or they can run a Debian 12 or older user-space
(in particular, not keeping up with the latest sbuild). However, if I'm
reading kernel git history correctly, the patch proposed on #1079124
should in principle work with any 4.7+ kernel (not tested). This would
not have been broad enough compatibility in 2017, but seems OK now.
smcv
Reply to: