Package: popularity-contest Version: 1.76 Severity: normal X-Debbugs-Cc: t...@mirbsd.de
-rw-r--r-- 1 root root 21239 Sep 26 11:06 popularity-contest -rw-r--r-- 1 root root 21260 Sep 26 06:25 popularity-contest.0 -rw-r--r-- 1 root root 4875 Sep 19 11:06 popularity-contest.1.gz -rw-r--r-- 1 root root 4883 Sep 19 06:25 popularity-contest.2.gz -rw-r--r-- 1 root root 4864 Sep 12 11:06 popularity-contest.3.gz -rw-r--r-- 1 root root 4893 Sep 12 06:25 popularity-contest.4.gz -rw-r--r-- 1 root root 4878 Sep 5 11:06 popularity-contest.5.gz -rw-r--r-- 1 root root 4871 Sep 5 06:25 popularity-contest.6.gz Probably caused by: -rw-r--r-- 1 root root 190 Nov 26 2023 /etc/cron.d/popularity-contest -rwxr-xr-x 1 root root 4892 Nov 3 2021 /etc/cron.daily/popularity-contest* AIUI, the former is generated from postinst to move the submission time around to avoid load spikes, whereas the latter, for some reason, is packaged, and it’ll always run at cron.daily time which will cause the load spikes the former is supposed to avoid. This system was upgraded from bullseye to bookworm on 2024-09-24 so this also affects bullseye, at the very least. -- System Information: Debian Release: 12.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'proposed-updates'), (500, 'stable') Architecture: armel (armv6l) Kernel: Linux 6.1.0-25-rpi (UP) Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to C.UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/lksh Init: sysvinit (via /sbin/init) Versions of packages popularity-contest depends on: ii debconf [debconf-2.0] 1.5.82 ii dpkg 1.21.22 Versions of packages popularity-contest recommends: ii cron [cron-daemon] 3.0pl1-162 pn gpg <none> ii postfix [mail-transport-agent] 3.7.11-0+deb12u1 Versions of packages popularity-contest suggests: pn anacron <none> pn tor <none> pn torsocks <none> -- debconf information: popularity-contest/submiturls: * popularity-contest/participate: true
