First of all, your language, "...apt and apt-get no longer permits [sic] weak-hash signatures" is incorrect. The weak signatures are still _permitted_; they just generate a warning.
Second, this _is_ an apticron bug in the sense that warnings the user can't do anything about that do not actually impact functionality should be suppressed, or at the very least there should be a configurable option to suppress them.
It is not a best practice for a program to generate warnings every single day that have no functional impact and the user can't do anything about. This wastes the user's time and tends to cause the user to ignore _other_ warnings that user can and should so something about.
Adding a setting to apticron.conf to suppress these warnings, with the setting disabled by default, would be sufficient to address this bug.
First of all, your language, "...apt and apt-get no longer permits [sic] weak-hash signatures" is incorrect. The weak signatures are still _permitted_; they just generate a warning.
Second, this _is_ an apticron bug in the sense that warnings the user can't do anything about that do not actually impact functionality should be suppressed, or at the very least there should be a configurable option to suppress them.
It is not a best practice for a program to generate warnings every single day that have no functional impact and the user can't do anything about. This wastes the user's time and tends to cause the user to ignore _other_ warnings that user can and should so something about.
Adding a setting to apticron.conf to suppress these warnings, with the setting disabled by default, would be sufficient to address this bug.