Package: strongswan-starter Version: 4.5.2-1.3 Severity: serious Justification: Policy 9.1.4
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. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
