Package: libdspam7-drv-sqlite3
Version: 3.9.1~rc1+git20110419.29261fb+dfsg-2
Severity: normal

Last night's cron.daily run yielded an error from
/etc/cron.daily/libdspam7-drv-sqlite3:

> /etc/cron.daily/libdspam7-drv-sqlite3: 10: cannot open 
> /usr/share/dspam/clean/purge-3.sql: No such file

It seems purge-3.sql somehow managed to wind up under
/usr/share/doc/libdspam-drv-sqlite3/sql; could you please move it to
where the script expects to find it?

Also, I see a couple of issues with the script itself:

- Because < is a shell metacharacter, the redirection will apply to
  the whole find command, with the effect that if multiple files
  match, only the first sqlite3 invocation will receive commands.  To
  address that, you'll need a shell loop:

if [ -d "$DSPAMHOME/data" ]; then
  find $DSPAMHOME/data -name "*.sdb" | while read x; do
    sqlite3 $x < /usr/share/dspam/clean/purge-3.sql
  done
fi

- The logic for setting DSPAMHOME could stand to be simpler; I'd recommend

DSPAMHOME=`awk '/^Home/ { print $2 }' $DSPAMCONF`

Could you please address all of those issues?  Thanks!

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.38-2-amd64 (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/dash

Versions of packages libdspam7-drv-sqlite3 depends on:
ii  lib 2.11.2-11                            Embedded GNU C Library: Shared lib
ii  lib 3.9.1~rc1+git20110419.29261fb+dfsg-2 Core message processing and classi
ii  lib 3.7.6.2-1                            SQLite 3 shared library
ii  sql 3.7.6.2-1                            Command line interface for SQLite 

libdspam7-drv-sqlite3 recommends no packages.

libdspam7-drv-sqlite3 suggests no packages.

-- Configuration Files:
/etc/dspam/dspam.d/sqlite.conf [Errno 13] Permission denied: 
u'/etc/dspam/dspam.d/sqlite.conf'

-- no debconf information



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to