On Sun, 26 Jul 2026 at 21:14, Bill Allombert <[email protected]> wrote:
> > i just want to know what it's going to send, without actually sending any > > mails to anyone. > > In /etc/popularity-contest.conf set > MAILTO="" > USEHTTP="no" > There should still be a logfile at /var/log/popularity-contest So this didnt quite work, but was enough of a hint: I think the intention with the cron approach was: a) at install time, $DAY is chosen randomly as a day of the week (date(1)'s %w) b) always submit on $DAY c) also submit if we ever notice it's been a week without a submission I think there are some issues in the current code (and one cron daily script could do both tasks), but hopefully i understood the idea I've implemented a MODE=--systemd that does the same using a systend timer, at https://salsa.debian.org/rpil2/popularity-contest/-/tree/systemd-timer?ref_type=heads - Ive added autopkgtests to test the logic as i understand it, ie the three bullets a, b, c above, i think this part is OK but im yet to test whether systemd actually schedules things as expected: i dont think it's quite ready to merge yet: there may be some edge cases i missed -- but i think you could take a look at the new code (ie debian/cron.daily) and see if it makes sense (and if the other changes made sense). while i was at it i modernised the packaging, and added the .gpg file to git (please check this is right - i just copied it from a random trixie system, but presumably you can verify the sha256sum etc) -- this fixes several lintian warnings (there are still issues with encodings in po files).
