Bug#1072105: /usr/lib/tmpfiles.d/legacy.conf:13: Duplicate line for path "/run/lock", ignoring.

[Richard Lewis]

On Tue, 28 May 2024 17:15:02 +0100 Luca Boccassi <bluca at debian.org> wrote:
> On Tue, 28 May 2024 17:44:54 +0200 Michael Biebl <biebl at debian.org>
> > Please do not not ship conflicting configuration for /run/lock
> >
> > /usr/lib/tmpfiles.d/debian.conf:d /run/lock    1777 root root -   -
> > /usr/lib/tmpfiles.d/legacy.conf:d /run/lock 0755 root root -

+1

this is really baffling for people who want to understand how debian
sets things up, -- what is the permission meant to be? why has debian
not made up its mind on what the permission is meant to be?

it gives the impression that something has not been thought about
properly, which is presumably not the intention?

If someone wanted to make a local change to permissions,  they would
presumably need to override both files?