Bug#500431: popularity-contest: cronned in daily instead of (announced on) weekly

2008-12-10 Thread Vagrant Cascadian
Package: popularity-contest Version: 1.45 Followup-For: Bug #500431 running from cron.daily on a specific day of the week makes it work poorly on systems not running all the time and relying on anacron to trigger weekly events; if i don't happen to boot my laptop on the appropriate day, it simply

Bug#500431: popularity-contest: cronned in daily instead of (announced on) weekly

2008-12-10 Thread Vagrant Cascadian
Package: popularity-contest Version: 1.45 Followup-For: Bug #500431 i added a workaround in /etc/popularity-contest.conf, by grabbing the check_stamp function from /etc/cron.daily/apt: check_stamp() { stamp=$1 interval=$2 if [ $interval -eq 0 ]; then return 1

Bug#500431: popularity-contest: cronned in daily instead of (announced on) weekly

2008-09-30 Thread Bill Allombert
On Sun, Sep 28, 2008 at 09:53:34AM +0200, William Dode wrote: Package: popularity-contest Version: 1.45 Severity: important The cron used for popularity-contest is now cron.daily On the man page it says weekly : Normally, popularity-contest is run from a cron(8) job,

Bug#500431: popularity-contest: cronned in daily instead of (announced on) weekly

2008-09-28 Thread William Dode
Package: popularity-contest Version: 1.45 Severity: important The cron used for popularity-contest is now cron.daily On the man page it says weekly : Normally, popularity-contest is run from a cron(8) job, /etc/cron.weekly/popularity-contest It affect popbugs on debian-goodies package when