https://bugzilla.novell.com/show_bug.cgi?id=406994 User max@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=406994#c2 Reinhard Max <max@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #2 from Reinhard Max <max@novell.com> 2008-07-08 05:30:59 MDT --- (In reply to comment #0 from Carlos Robinson)
Even after the recent YOU update of clamav to 0.93.1-0.1 and clamav-db to 0.93.1-0.1, the daemon still complains that it is outdated
It looks like the ClamAV team recently stopped notifying binary packagers in advance of new releases, giving them some time to prepare their packages.
It is absurd to have this warning popping up in the warn log every two hours if it is not true, and dangerous if it is true.
I asked in the security list and Marcus Meissner told me that the clamav people have changed again the version number; maybe they could find someway easier way?
Please try talking to the ClamAV people yourself, maybe they start listening if more people speak up. I have given up on getting ignored or rejected when suggesting ways to make these update notifications from freshclam more to the point, so that an admin or user can distinguish between normal updates with bugfixes or improvements to the engine and urgent security updates.
Some automated method that makes upgrading the engine and the database a triffle?
I don't know what a triffle is, but the database is already being upgraded automatically by freshclam, which is fine, but we certainly wouldn't want to handle the engine the same way, as it would defeat the purpose of having it packaged as an RPM. BTW, I'll immediately prepare the new ClamAV packages... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.