On Mon, 2012-04-09 at 20:50 +0200, René Mayrhofer wrote: > 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.
Policy section 9.1.4: Packages must not include files or directories under `/run', or under the older `/var/run' and `/var/lock' paths. The latter paths will normally be symlinks or other redirections to `/run' for backwards compatibility. Policy section 9.3.2: Files and directories under `/run', including ones referred to via the compatibility paths `/var/run' and `/var/lock', are normally stored on a temporary filesystem and are normally not persistent across a reboot. The `init.d' scripts must handle this correctly. This will typically mean creating any required subdirectories dynamically when the `init.d' script is run. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
