Bug#1115317: advice for using /var/lock (which is a link to /run/lock) (#1110981)

Thorsten Alteholz <[email protected]> Mon, 15 Sep 2025 14:26:29 +0000 (UTC)
Newsgroups gmane.linux.debian.devel.ctte
Message-ID <b74edbae-4e43-93f5-b8a7-52dc5695601c__905.12548792816$1757947650$gmane$org@alteholz.de>
Package: tech-ctte
Severity: normal


Hi,

I am a bit stuck with #1110981 and need your advice on how to proceed.

Due to a change in systemd, the directory /run/lock is no longer world 
writable, but uucp uses this directory to create its lock files (as it is 
documented in FHS). As you can see in #1110981 there already is a 
complaint from a user that uucp no longer works.

The corresponding bug #1110980 in systemd was marked as "wontfix". So 
what do you recommend how to go on from here? Change Debian policy (as 
asked in #1111839), revert the change in systemd, find a Debian wide 
solution or let every package maintainer implement their own solution?

   Thorsten

Relevant bugs up to now:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1110981
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1110980
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1111839