Bug#1085308: systemd: both /usr/lib/tmpfiles.d/{debian.conf, legacy.conf} declare /run/lock

[Andreas Beckmann]

Package: systemd
Version: 256.7-1
Severity: important

Installing systemd in a minimal pbuilder sid chroot produces a warning
in bold face:


Setting up systemd (256.7-1) ...
Created symlink '/etc/systemd/system/getty.target.wants/getty at tty1.service' -> '/usr/lib/systemd/system/getty at .service'.
Created symlink '/etc/systemd/system/multi-user.target.wants/remote-fs.target' -> '/usr/lib/systemd/system/remote-fs.target'.
Created symlink '/etc/systemd/system/sysinit.target.wants/systemd-pstore.service' -> '/usr/lib/systemd/system/systemd-pstore.service'.
<BOLD>/usr/lib/tmpfiles.d/legacy.conf:13: Duplicate line for path "/run/lock", ignoring.</BOLD>


I suspect that warning will also show when upgrading systemd on a
"normal" system.


The two files are also setting different permissions:

/usr/lib/tmpfiles.d/debian.conf:d /run/lock    1777 root root -   -
/usr/lib/tmpfiles.d/legacy.conf:d /run/lock 0755 root root -


Andreas