Le 26/01/21 à 13:44, Julian Andres Klode a écrit :
On Tue, Jan 26, 2021 at 12:52:52PM +0100, Aurelien Jarno wrote:
reassign 979970 src:glibc,src:libselinux,src:apt,src:openssh
thanks
On 2021-01-25 11:59, Laurent Bigonville wrote:
reassign 979970 src:glibc 2.30-1
affects 979970 + libselinux1
Package: tracker.debian.org
X-Debbugs-Cc: pkg-javascript-de...@lists.alioth.debian.org
Severity: important
For yarnpkg: https://tracker.debian.org/pkg/node-yarnpkg
tracker.debian.org reports:
uscan had problems while searching for a new upstream version:
unrecognized option ctype=nodejs
On Thu, 2021-01-28 at 09:17 +0100, Stephen Kitt wrote:
> ... except it does, which is the problem you ran into:
Argh, forgot about the cause of that issue...
> See #939767 for my proposed fix...
Seems like that needs sending upstream.
--
bye,
pabs
https://wiki.debian.org/PaulWise
On Thu, Jan 28, 2021 at 09:05:55AM +0100, Paul Gevers wrote:
> We generate fresh containers on a daily basis.
I suppose you can check AppArmor logs, perhaps it is only enabled or
configured differently on this host.
--
Valentin
Hello Bastien,
On 1/27/21 4:48 PM, roucaries.bast...@gmail.com wrote:
> From: Bastien Roucariès
>
> Some variables are portable at least under UNIX
>
> Signed-off-by: Bastien Roucariès
> ---
> man7/environ.7 | 11 +++
> 1 file changed, 11 insertions(+)
>
> diff --git
reassign 981201 xvfb
thanks
I've submitted a pull request against xvfb-run to achieve this.
https://salsa.debian.org/xorg-team/xserver/xorg-server/-/merge_requests/6
Hopefully the X strike force folks will look at it kindly.
FWIW, the way this can be reproduced easily even on amd64 is:
1. in
Hello Bastien,
On 1/27/21 4:48 PM, roucaries.bast...@gmail.com wrote:
> From: Bastien Roucariès
>
> Clearly document that su by default does not change this variables.
I'm dubious about this. The place that this should be (and is)
properly documented is the manual page for su(1). Why repeat it
On Thu, 28 Jan 2021 06:31:44 +0800, Paul Wise wrote:
> On Wed, 2021-01-27 at 20:08 +0100, Stephen Kitt wrote:
> > No worries, they’re still bugs affecting loggedfs! I’ll downgrade
> > this one and fix the other. (I’ll also suggest a fix for the nonempty
> > handling in fuse3...)
>
> I had a
Control: tags 939767 + patch
Dear maintainer,
I've prepared a patch which restores support for "-o nonempty", thus
allowing programs using that option with fuse to continue working
as-is with fuse3 (where the default behaviour is equivalent to "-o
nonempty").
I can upload an NMU if it's helpful
Hi,
On 27-01-2021 22:41, Valentin Vidic wrote:
> On Wed, Jan 27, 2021 at 10:37:56PM +0100, Paul Gevers wrote:
>> debian@ci-worker-ppc64el-01:~$ sudo cat /etc/lxc/default.conf
>> # MANAGED WITH CHEF; DON'T CHANGE BY HAND
>> lxc.net.0.type = veth
>> lxc.net.0.link = virbr0
>> lxc.net.0.flags = up
Hi,
On 27-01-2021 23:00, Chris Hofstaedtler wrote:
> TTBOMK this means some namespacing and/or protection feature
> implemented by systemd is broken on this worker. I don't know if
> this is a kernel, systemd, libc or some other problem, but it's
> not a pdns(-recursor) problem.
Ack.
> Maybe
201 - 211 of 211 matches
Mail list logo
