Package: webcalendar
Version: 1.2.0+dfsg-4
Severity: normal

The test for whether to run the cron script should include checking for
the presence of the php script.  I'd suggest this test:

  [ -d /usr/share/webcalendar -a -x 
/usr/share/webcalendar/tools/send_reminders.php ]

-- System Information:
Debian Release: 5.0.1
  APT prefers stable
  APT policy: (501, 'stable'), (50, 'unstable')
Architecture: i386 (i686)

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

Versions of packages webcalendar depends on:
ii  apache2            2.2.9-10+lenny3       Apache HTTP Server metapackage
ii  apache2-mpm-prefor 2.2.9-10+lenny3       Apache HTTP Server - traditional n
ii  dbconfig-common    1.8.39                common framework for packaging dat
ii  debconf [debconf-2 1.5.24                Debian configuration management sy
ii  libapache2-mod-php 5.2.6.dfsg.1-1+lenny3 server-side, HTML-embedded scripti
pn  libjs-prototype    <none>                (no description available)
ii  php5-cli           5.2.6.dfsg.1-1+lenny3 command-line interpreter for the p
ii  php5-mysql         5.2.6.dfsg.1-1+lenny3 MySQL module for php5
ii  php5-pgsql         5.2.6.dfsg.1-1+lenny3 PostgreSQL module for php5
ii  ucf                3.0016                Update Configuration File: preserv

Versions of packages webcalendar recommends:
ii  mysql-client-5.0 [mysq 5.0.51a-24+lenny1 MySQL database client binaries
ii  mysql-server-5.0 [mysq 5.0.51a-24+lenny1 MySQL database server binaries
ii  postgresql             8.3.7-0lenny1     object-relational SQL database (su
ii  postgresql-client      8.3.7-0lenny1     front-end programs for PostgreSQL 
ii  postgresql-client-8.3  8.3.7-0lenny1     front-end programs for PostgreSQL 
ii  sqlite3                3.5.9-6           A command line interface for SQLit

Versions of packages webcalendar suggests:
ii  php5-gd            5.2.6.dfsg.1-1+lenny3 GD module for php5
pn  php5-ldap          <none>                (no description available)



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

Reply via email to