Over the last several weeks I've been trying to get caught up on my Debian work after having been absent for awhile. Sebastian, thanks for keeping clamav up to date.
Since it looks like you have clamav itself well in hand, I haven't done anything with it. I did update clamtk to the newest release. I've uploaded the upstream cvdupdate tool to New as clamav-cvdupdate. It is pretty easy to get blacklisted by attempting too many data downloads. Anyone with a non-trivial number of systems is going to end up running a private mirror for the data, so it seems like the upstream blessed tool to download the data without freshclam is something we should provide to users. I was also looking at adding an autopkgtest to pyclamd and while I got it mostly working (it needs a running clamd), each test run downloaded the data and I was quickly over my quota. I don't think running autopkgtests for clamav related packages will scale very well if they all download data for the tests. I am considering if we should resurrect the clamav-data package, not as an auto-generated, auto-uploaded (which are the reasons it got removed before) 'current' version of the clamav data, but as a test data repository that we can depend on for tests to run them without hitting the clamav mirrors. If we did that, we could make it an alternate depends with freshclam, as it was before. That's what's up on the clamav front from my end. Anything else I can help with? Scott K
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Pkg-clamav-devel mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-clamav-devel
