Bug#961655: debhelper: compat 13 HOME and XDG_RUNTIME_DIR are long enough to break AF_UNIX sockets

2020-06-28 Thread Niels Thykier
Simon McVittie: > On Sun, 28 Jun 2020 at 11:08:36 +0200, Niels Thykier wrote: >> [...] > > The workaround in mutter[1] isn't *too* awful. The most problematic > thing about it is that the logic for it has to be "inside" dh_auto_test; > setting the XDG_RUNTIME_DIR in d/rules is no longer

Bug#961655: debhelper: compat 13 HOME and XDG_RUNTIME_DIR are long enough to break AF_UNIX sockets

2020-06-28 Thread Simon McVittie
On Sun, 28 Jun 2020 at 11:08:36 +0200, Niels Thykier wrote: > Simon McVittie: > > For now I'm going to put a workaround in mutter to create its own > > temporary XDG_RUNTIME_DIR, but it seems a shame not to be able to take > > advantage of debhelper solving this problem centrally. > > Finally,

Bug#961655: debhelper: compat 13 HOME and XDG_RUNTIME_DIR are long enough to break AF_UNIX sockets

2020-06-28 Thread Mattia Rizzolo
On Sun, Jun 28, 2020 at 11:08:36AM +0200, Niels Thykier wrote: > The relevant question here being whether /tmp is cleaned automatically > by sbuild, pbuilder (etc.) on errors. If it is, then this approach > might be a non-issue. I think nothing should start relying on chroot-controllers to clean

Bug#961655: debhelper: compat 13 HOME and XDG_RUNTIME_DIR are long enough to break AF_UNIX sockets

2020-06-28 Thread Niels Thykier
Simon McVittie: > Package: debhelper > Version: 13.1 > Severity: important > > After the release of debhelper 13.1, mutter fails to build from source > with test failures. I can reproduce the build failure with a previous > version of mutter that used to build successfully. > > [...] > > In

Bug#961655: debhelper: compat 13 HOME and XDG_RUNTIME_DIR are long enough to break AF_UNIX sockets

2020-05-27 Thread Simon McVittie
Package: debhelper Version: 13.1 Severity: important After the release of debhelper 13.1, mutter fails to build from source with test failures. I can reproduce the build failure with a previous version of mutter that used to build successfully. >From the build log, the failing tests are failing