Ubuntu Forums - View Single Post

kitterma

There are a few points no one mentioned....

If you are on Feisty (at least, maybe earler, I tested Feisty) and install all the build dependencies, you can use the klamav GUI to keep your clamav current if you want.

The jump from 0.8x to 0.9x changed the interfaces between clamav and the packages that depend on it and also change the library from libclamav1 to libclamav2. As a result, if you just backported the current clamav to Dapper and Edgy, it'd break a number of packages (in fact the clamtk we released with Feisty is essentially useless because an updated clamtk was available in time that would work with clamav 0.9x - I've asked for a backport of the Gutsy version that does work, but it's still pending).

The why is, of course, not enough volunteers. As Laserjock mentioned we are trying to figure out the most workable solution to this problem. No matter what solution we use, we'll need help with testing and packaging. If anyone is interested in helping and not just whining about the problem, look me up (ScottK) on #ubuntu-motu on IRC.

June 20th, 2007	#46
kitterma Ubuntu Developer Join Date: May 2006 Beans: 32 Kubuntu Karmic Koala (testing)	Re: Why is ClamAV NOT being maintained? There are a few points no one mentioned.... If you are on Feisty (at least, maybe earler, I tested Feisty) and install all the build dependencies, you can use the klamav GUI to keep your clamav current if you want. The jump from 0.8x to 0.9x changed the interfaces between clamav and the packages that depend on it and also change the library from libclamav1 to libclamav2. As a result, if you just backported the current clamav to Dapper and Edgy, it'd break a number of packages (in fact the clamtk we released with Feisty is essentially useless because an updated clamtk was available in time that would work with clamav 0.9x - I've asked for a backport of the Gutsy version that does work, but it's still pending). The why is, of course, not enough volunteers. As Laserjock mentioned we are trying to figure out the most workable solution to this problem. No matter what solution we use, we'll need help with testing and packaging. If anyone is interested in helping and not just whining about the problem, look me up (ScottK) on #ubuntu-motu on IRC.