On Jun 16, 2005, at 2:19 PM, Joshua Penix wrote:
Unfortunately, it's Debian's fault for the outdated ClamAV. They
froze at 0.84 because they froze the distro. While that works
quite well for most packages, it's not a good policy for ClamAV.
John, how do Debian people handle stuff like that? Or should we
rip out the package and replace it with a source install and auto-
updating script?
Well I answered my own question. Per ClamAV's site (http://
www.clamav.net/binary.html), they point to the Debian Volatile
project (http://volatile.debian.net/), which exists for exactly this
purpose.
I added an apt source as follows (John please check my syntax on this):
deb http://volatile.debian.net/debian-volatile sarge/volatile main
Unfortunately it doesn't look like more current ClamAV has shown up
there yet, but hopefully in a few days the errors we're seeing in the
system log will go away.
--
Joshua Penix http://www.binarytribe.com
Binary Tribe Linux Integration Services & Network Consulting
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-steer
