package: piuparts.debian.org Hi,
piuparts.d.o sends too many mails per day, currently 34, while 1-3 would be acceptable. This is how it looks in mutt for yesterday: 19 Oct 31 Cron Daemon ( 37K) [Piuparts-reports] Cron <piupartsm@pejacevic> detect_piuparts_issues 20 Oct 31 piuparts master ( 18K) [Piuparts-reports] archive_old_logs 21 Oct 31 Cron Daemon (2.7K) [Piuparts-reports] Cron <piupartsm@pejacevic> detect_well_known_errors 22 Oct 31 Cron Daemon (0.4K) [Piuparts-reports] Cron <piupartsm@pejacevic> rotate_master_logs 23 Oct 31 Cron Daemon (5.8K) [Piuparts-reports] Cron <piupartsm@pejacevic> detect_network_issues 24 Oct 31 Cron Daemon (561K) [Piuparts-reports] Cron <piupartsm@pejacevic> piuparts-report 25 Oct 31 Cron Daemon (9.0K) [Piuparts-reports] Cron <piupartsm@pejacevic> report_untestable_packages 26 Oct 31 Cron Daemon (2.6K) [Piuparts-reports] Cron <piupartsm@pejacevic> detect_archive_issues 27 Oct 31 Cron Daemon (7.8K) [Piuparts-reports] Cron <piupartsm@pejacevic> detect_well_known_errors 28 Oct 31 Cron Daemon (110K) [Piuparts-reports] Cron <piupartsm@pejacevic> piuparts-analyze 29 Oct 31 Cron Daemon (446K) [Piuparts-reports] Cron <piupartsm@pejacevic> detect_piuparts_issues 30 Oct 31 Cron Daemon (4.2K) [Piuparts-reports] Cron <piupartsm@pejacevic> detect_network_issues 31 Oct 31 Cron Daemon (3.5K) [Piuparts-reports] Cron <piupartsm@pejacevic> detect_well_known_errors 32 Oct 31 Cron Daemon ( 95K) [Piuparts-reports] Cron <piupartsm@pejacevic> detect_piuparts_issues 33 Oct 31 Cron Daemon (2.4K) [Piuparts-reports] Cron <piupartsm@pejacevic> detect_network_issues 34 Oct 31 Cron Daemon (541K) [Piuparts-reports] Cron <piupartsm@pejacevic> piuparts-report 35 Oct 31 Cron Daemon (2.5K) [Piuparts-reports] Cron <piupartsm@pejacevic> detect_well_known_errors 36 Oct 31 Cron Daemon ( 18K) [Piuparts-reports] Cron <piupartsm@pejacevic> reschedule_oldest_logs 37 Oct 31 Cron Daemon ( 54K) [Piuparts-reports] Cron <piupartsm@pejacevic> detect_piuparts_issues 38 Oct 31 Cron Daemon (3.2K) [Piuparts-reports] Cron <piupartsm@pejacevic> detect_well_known_errors 39 Oct 31 Cron Daemon ( 53K) [Piuparts-reports] Cron <piupartsm@pejacevic> detect_piuparts_issues 40 Oct 31 Cron Daemon (2.1K) [Piuparts-reports] Cron <piupartsm@pejacevic> detect_network_issues 41 Oct 31 Cron Daemon ( 11K) [Piuparts-reports] Cron <piupartsm@pejacevic> detect_archive_issues 42 Oct 31 Cron Daemon (745K) [Piuparts-reports] Cron <piupartsm@pejacevic> piuparts-report 43 Oct 31 Cron Daemon (1.9K) [Piuparts-reports] Cron <piupartsm@pejacevic> detect_well_known_errors 44 Oct 31 Cron Daemon ( 39K) [Piuparts-reports] Cron <piupartsm@pejacevic> detect_piuparts_issues 45 Oct 31 Cron Daemon (2.3K) [Piuparts-reports] Cron <piupartsm@pejacevic> detect_network_issues 46 Oct 31 Cron Daemon ( 96K) [Piuparts-reports] Cron <piupartsm@pejacevic> piuparts-analyze 47 Oct 31 Cron Daemon ( 35K) [Piuparts-reports] Cron <piupartsm@pejacevic> detect_piuparts_issues 48 Oct 31 Cron Daemon (7.8K) [Piuparts-reports] Cron <piupartsm@pejacevic> detect_network_issues 49 Oct 31 Cron Daemon (3.7K) [Piuparts-reports] Cron <piupartsm@pejacevic> detect_well_known_errors 50 Oct 31 Cron Daemon (112K) [Piuparts-reports] Cron <piupartsm@pejacevic> reschedule_oldest_logs 51 Oct 31 Cron Daemon (123K) [Piuparts-reports] Cron <piupartsm@pejacevic> detect_piuparts_issues 52 Oct 31 Cron Daemon (498K) [Piuparts-reports] Cron <piupartsm@pejacevic> piuparts-report 53 Oct 31 piuparts master ( 40K) [Piuparts-reports] generate_daily_report I think I only want one mail per day, with the daily report. That mail could include all the others as attachments or have links to https://piuparts.debian.org/logs/20181031/detect_well_known_errors.1.html or whatever. An improvement would also be to collect them and then only send one mail per type per day. -- cheers, Holger ------------------------------------------------------------------------------- holger@(debian|reproducible-builds|layer-acht).org PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C
signature.asc
Description: PGP signature
