On Jun 16, 2005, at 12:12 PM, Neil Schneider wrote:
Today, I was trying to figure out how we can upgrade clamAV to get rid of the messages coming from the server about it being out of date. I ran apt-get upgrade and was told there are 92 packages to upgrade. I found it interesting that clamAV was not on the list. I aborted, because I didn't want to break anything on the server. I disussed this with JHRIV on IRC and we concluded we don't really know who is responsible. It's probably important that at least some of these packages be upgraded. Who should take care of this?
I've been taking care of it mostly because it's my bandwidth that gets eaten if the server gets hacked. :)
Last update I did was a couple weeks ago, I then paused waiting for Sarge to hit officially. Now is probably a good time to do the updates.
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?
All that said, I'm going to go ahead and apply the patches right now and bring us up to full Sarge.
-- 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
