I upgraded to the -backports version and have noticed no problems - all the client apps that rely on Clam here (a few scripts, a Thunderbird plugin, and the havp scanning proxy) seem to be quite happy.
(The only tiny glitch was having to merge in config file changes due to new and discontinued options - seems to happen fairly often with ClamAV. Would it make sense to go to a system like gdm uses, where user customizations are stored in a separate file, allowing the base config to be changed underneath on version upgrades? A bit of sed magic in the init.d script would probably do the trick..)
I upgraded to the -backports version and have noticed no problems - all the client apps that rely on Clam here (a few scripts, a Thunderbird plugin, and the havp scanning proxy) seem to be quite happy.
(The only tiny glitch was having to merge in config file changes due to new and discontinued options - seems to happen fairly often with ClamAV. Would it make sense to go to a system like gdm uses, where user customizations are stored in a separate file, allowing the base config to be changed underneath on version upgrades? A bit of sed magic in the init.d script would probably do the trick..)