calamaris (2.99.4.0-12) unstable; urgency=low In previous version, it was not possible to run calamaris after squid (out of /etc/logrotate.d/squid for instance). With this release, this is possible. Change the setting of cachefile in /etc/calamaris/cron.conf and remove the script /etc/cron.daily/calamaris. -- Philipp Frauenfelder Fri, 15 Apr 2011 22:08:01 +0200 calamaris (2.99.4.0-5) unstable; urgency=low In previous versions, there was a problem with the graphics created along with the HTML report: The graphics of the daily, weekly and monthly report all had the same name and were stored in the same directory. This was fixed in 2.99.4.0-4 by assigning different directories to these reports in the default configuration. You might want to adapt your configuration as well by editing /etc/calamaris/cron.conf or by using 'dpkg-reconfigure calamaris'. For details, please refer to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=453142 -- Philipp Frauenfelder Tue, 04 Dec 2007 19:57:06 +0100 calamaris (2.99.1.3-1) unstable; urgency=low Version 3 of Calamaris can now be configured using a configuration file. Its name is /etc/calamaris/calamaris.conf. The configuration file for the cron script running calamaris daily was perviously installed in /etc/calamaris.conf and has been moved to /etc/calamaris/cron.conf. This file is managed with debconf. You can use 'dpkg-reconfigure calamaris' to changed its values or change the file directly. You can delete the old file /etc/calamaris.conf if you want. It is no longer used. -- Philipp Frauenfelder Tue, 04 Dec 2007 20:01:00 +0100 calamaris (2.42-1) unstable; urgency=low Starting with this release, the Calamaris package uses debconf to manage the configuration file for the cron script: /etc/calamaris.conf. You can use 'dpkg-reconfigure calamaris' to change the behaviour or change the configuration file directly. -- Philipp Frauenfelder Tue, 28 Aug 2001 14:41:27 +0000