[Logcheck-devel] Bug#558995: logcheck: Should avoid "no shuch file/dir" errors during new installs

[Frans Pop]

Package: logcheck
Version: 1.3.3
Severity: minor

During a new installation of logcheck I got the following errors:
Setting up logcheck (1.3.3) ...
Adding user logcheck to group adm
chown: cannot access `/var/lock/logcheck': No such file or directory
chmod: cannot access `/var/lock/logcheck': No such file or directory
chown: cannot access `/var/lock/logcheck': No such file or directory

It would be cleaner to avoid these, and it should be trivial to do so.

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: hppa (parisc64)

Kernel: Linux 2.6.32-rc5 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages logcheck depends on:
ii  adduser            3.111                 add and remove users and groups
ii  bsd-mailx [mailx]  8.1.2-0.20090911cvs-2 simple mail user agent
ii  cron               3.0pl1-106            process scheduling daemon
ii  exim4              4.69-11               metapackage to ease Exim MTA (v4) 
ii  exim4-daemon-light 4.69-11+b1            lightweight Exim MTA (v4) daemon
ii  lockfile-progs     0.1.13                Programs for locking and unlocking
ii  logtail            1.3.3                 Print log file lines that have not
ii  sysklogd [system-l 1.5-5                 System Logging Daemon

Versions of packages logcheck recommends:
ii  logcheck-database             1.3.3      database of system log rules for t

Versions of packages logcheck suggests:
pn  syslog-summary                <none>     (no description available)

-- no debconf information