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 doesn't run.
i think it would be be better to check the last time /var/log/popularity-contest was updated, and run popularity-contest only if it hadn't been updated in 7 days (or a configurable number, like /etc/cron.daily/apt). this should give a fairly random distribution (based on install dates), while still allowing for systems that are not running all the time to function. live well, vagrant -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing'), (101, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) 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 popularity-contest depends on: ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy ii dpkg 1.14.23 Debian package management system Versions of packages popularity-contest recommends: ii cron 3.0pl1-105 management of regular background p ii exim4 4.69-9 metapackage to ease Exim MTA (v4) ii exim4-daemon-light [mail-tran 4.69-9 lightweight Exim MTA (v4) daemon Versions of packages popularity-contest suggests: ii anacron 2.3-13.1 cron-like program that doesn't go -- debconf information: popularity-contest/submiturls: * popularity-contest/participate: true -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]