2012/4/19 Michael Vogt <m...@debian.org>: > Right, so I added the print there on purpose to ensure that users are > informed that there is a package held back. It maybe the wrong > tradeoff, in the current version I added code that will only print if > there is no summary mail. That may still not be enough and I may need > to remove it entirely.
I have a strong opinion on this subject: Cron should not send any email unless there was an error or it was explicitly configured to do so by the Sysadmin. :-) > My goal is to ensure that people are not > running unattended-upgrades assuming they are safe when in fact a > conffile issue holds a package back (and because they never look at > the logs they don't know). I'm open for ideas what could be done > instead, maybe just doing the print only once instead of everytime > that cron is run? If you really think this should be done (I don't) than you should make it configurable via U-A::Print-Warning-to-Cron or something similar which should default to "false". Thinking a little more about this I think this kind of already exists via U-A::MailOnlyOnError. So maybe a new option named U-A::Mail-if-Packages-on-Hold could complement this one — I'm assuming these are simply ignored if U-A::Mail is set. BTW, there is some inconsistent naming on these options — some are using '-' character others do not. I think you should use one style for all of them, the other should remain supported but deprecated. Thanks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
