On 06.04.2012 17:32, Aristov Max wrote:
According to DP "/run is cleared at boot", so some changes should be made to
the upstream code, for example strongswan could keep files directly in /run/lock
directory.
I noticed the problem, when configuration of base-files failed in multistrapped
environment: its postinst script assumes /var/lock to be empty.
The subdirectory under /var/lock is used to restrict its permissions for
more secure locking, and upstream will most probably not change it. I do
not currently agree that this is in violation to Debian Policy, so
unless you can convince me that a change will indeed improve the
package, I will mark this as wontfix and lower the priority to normal.
best regards,
Rene
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
