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

Luca Boccassi bluca at debian.org
Wed May 29 19:24:27 BST 2024


Control: close -1

On Wed, 29 May 2024 20:15:36 +0200 Michael Biebl <biebl at debian.org>
wrote:
> Control: reopen -1
> 
> On Tue, 28 May 2024 17:15:02 +0100 Luca Boccassi <bluca at debian.org>
wrote:
> > Control: tags -1 wontfix
> > Control: close -1
> > 
> > On Tue, 28 May 2024 17:44:54 +0200 Michael Biebl <biebl at debian.org>
> > wrote:
> > > Package: systemd
> > > Version: 256~rc3-4
> > > Severity: normal
> > > 
> > > 
> > > 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 -
> > > 
> > > triggering unnecessary warnings.
> > 
> > This is needed to apply debian-specific changes, just ignore it,
it's
> > harmless
> 
> Besides the obvious warning message, shipping conflicting tmpfiles 
> configuration snippets also has the problem, that depending on which 
> file you override, one or the other becomes active.
> 
> Say you create a /etc/tmpfiles.d/debian.conf, then the configuration
in 
> legacy.conf becomes active and vise versa.
> This is highly confusing.

Yes, that is normal - if you change something, you need to check what's
there and what's not. This is not a new problem.

> tmpfiles entries are not easily overridable, as the mechanism is per 
> file and not per entry.
> 
> So, either legacy.conf gets split up so individual entries can be 
> overridden or your patch legacy.conf.
> 
> The current approach is not sufficient.

No. The current approach is just fine. If you don't like seeing the
harmless notice-level log, just add a local override in /etc/.

> Btw, please don't close bug reports without CCing the bug submitter. 
> That's rude.

Please stop playing ping pong with the BTS, this is staying as it is.

-- 
Kind regards,
Luca Boccassi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20240529/6d103d18/attachment.sig>


More information about the Pkg-systemd-maintainers mailing list