Package: unattended-upgrades
Version: 2.8

I checked the source of unattended-upgrades and found, that the setting of the 
frontend is set to mail, if sendmail exists and to none if it doesn’t. However, 
if set to mail as described in the comment without checking for an existing 
sendmail makes sense, but it doesn’t make sense, if listchanges.conf has 
another setting yet (e.g. none) and it is not intended to send listchanges 
mails or show any of the changes in the unattended.upgrades mail as well, e.g. 
because of using apticron already for a structured mail of all changes. So 
would be nice to be able to disable listchanges and/or first check the config, 
if something else is set instead of mail, before doing the bug related check of 
sendmail for sending mails and overwriting any existing value to mail, if it 
exist.

Reply via email to