Clamav

Differences between revisions 303 and 305 (spanning 2 versions)
Revision 303 as of 2011-10-29 18:35:06
Size: 7524
Editor: cemc
Comment: 0.97.3 on natty, oneiric: mimedefang, p3scan OK
Revision 305 as of 2011-10-29 19:24:48
Size: 7600
Editor: cemc
Comment: 0.93.7 on natty, oneiric: clamsmtp, exim4, pyclamd, libclamav-client-perl OK
Deletions are marked like this. Additions are marked like this.
Line 85: Line 85:
|| [[MOTU/Clamav/TestingProcedures#qpsmtpd|qpsmtpd]] || || || || || || || || [[MOTU/Clamav/TestingProcedures#qpsmtpd|qpsmtpd(1)]] || || || || OK || '''OK''' || ||
Line 94: Line 94:
|| [[MOTU/Clamav/TestingProcedures#clamfs|clamfs]] || || || || || || ||
|| [[MOTU/Clamav/TestingProcedures#clamsmtp|clamsmtp]] || || || || || ||  ||
|| [[MOTU/Clamav/TestingProcedures#clamfs|clamfs]] || || || || OK || '''OK''' || ||
|| [[MOTU/Clamav/TestingProcedures#clamsmtp|clamsmtp]] || || || || OK || '''OK''' || ||
Line 99: Line 99:
|| [[MOTU/Clamav/TestingProcedures#exim4|exim4]] || || || || || || || || [[MOTU/Clamav/TestingProcedures#exim4|exim4]] || || || || OK || '''OK''' || ||
Line 101: Line 101:
|| [[MOTU/Clamav/TestingProcedures#perl|libclamav-client-perl]] || || || || || ||  || || [[MOTU/Clamav/TestingProcedures#perl|libclamav-client-perl]] || || || || OK || '''OK''' || ||
Line 105: Line 105:
|| [[MOTU/Clamav/TestingProcedures#mimedefang|mimedefang]] || || || || || || || || [[MOTU/Clamav/TestingProcedures#mimedefang|mimedefang]] || || || || OK || '''OK''' || ||
Line 107: Line 107:
|| [[MOTU/Clamav/TestingProcedures#pyclamd|pyclamd]] || || || || || ||  || || [[MOTU/Clamav/TestingProcedures#pyclamd|pyclamd]] || || || || OK || '''OK''' || ||

Status

ubuntu-clamav PPA

Cleared matrix for clamav-0.97.3 testing. No SO version change, so it's still libclamav6, no major problems anticipated.

The libclamav6 transition is done for Hardy.

Note: Starting with 0.94, clamav now has an apparmor profile, so these backports may have issues related to apparmor.

clamav-0.96.5 is in maverick/lucid-updates.

clamav-0.97 is in natty. 0.97.2 is in oneiric, natty-updates, and hardy/lucid/maverick-backports. clamav-0.97.3 is in precise and uploaded to natty/oneiric-proposed for testing.


Steps for Clamav Backport

  • Step one is to publish a draft package for a clamav <version> backport to older releases out for people to use. The draft source package can be found in the PPA.

  • Step two is to prepare backports of the libclamav rdepends, upload them to the PPA, and then work on patching packages that don't build.
  • Step three is testing the backports from the PPA. Indicate test results below. All libclamav rdepends must be tested. Unless there are documented changes in the clamav-dameon (clamd) protocol, only a sampling of clamav-daemon rdepends need to be tested.
  • Step four is massive backport of all of the needed updates at the same time so nothing (promise) breaks.
  • Step five: Move to another release, rinse, repeat.

Testing procedures can be found here or by clicking on the package names in the matrix below. Feel free to complete missing testing procedures.

Steps for copying Clamav to -updates/ -security

Once clamav and any needed rdepends are in *-backports, a close watch on bug reports for all related packages must be maintained. The step to *-backports brings the new clamav version to a wider audience for testing. The purpose if using *-backports is to enable wide testing and early access to users that require it while leaving -proposed open for any urgent fixes that need to be pushed on through.

Once the package set has aged sufficiently (generally a week without new bug reports is generally sufficient) then it should be copied to either *-security or *-updates. Virtually all clamav releases include security fixes, so it is likely that *-security will be the initial target and then the packages will be automatically copied to *-updates. The Ubuntu security team will rebuild all the packages in the Ubuntu security PPA if the target is *-security. If the target is *-updates, the Ubuntu SRU can pocket copy the packages from *-backports.

Packages

The following matrices indicate the testing phase for every package which depends/uses clamav. Packages which can use multiple methods of scanning (ie. clamd, clamdscan, clamscan) will be listed in each matrix and have to be tested accordingly. Matrix values:

  • X - package n/a in that particular release, or cannot be tested

  • OK - package was tested and it works without problems

  • <blank> - package is being tested / was not tested yet

  • any other short comment...

Packages built with libclamav (libclamav rdepends), these need to be tested before any other package:

  • testing libclamav6/clamav0.97.3

Packages

Hardy

Lucid

Maverick

Natty

Oneiric

Precise

dansguardian

OK

OK

gurlchecker

havp

OK

OK

klamav

X

X

python-clamav

OK

OK

php4-clamavlib

X

X

X

X

X

php5-clamavlib

X

X

X

X

X

php-clamav(1)

X

X

X

OK

OK

Note1: php-clamav is NOT in any release yet, only in the clamav-ppa

Packages which integrate with clamav through clamscan/clamdscan:

  • testing libclamav6/clamav0.97.3

Packages

Hardy

Lucid

Maverick

Natty

Oneiric

Precise

amavisd-new

OK

OK

clamassassin

OK

OK

clamtk

OK

OK

dansguardian

OK

OK

kmail (suggests)

OK

OK(!)

mediawiki

mimedefang

OK

OK

moodle (suggests)

nautilus-clamscan

p3scan

OK

OK

qpsmtpd(1)

OK

OK

Note1: problems using clamscan in ALL releases, only works with backported package in Hardy; clamdscan works (https://bugs.launchpad.net/bugs/829649)

Packages which integrate with clamav via the clamav-daemon socket protocol:

  • testing libclamav6/clamav0.97.3

Packages

Hardy

Lucid

Maverick

Natty

Oneiric

Precise

amavisd-new

OK

OK

clamfs

OK

OK

clamsmtp

OK

OK

dspam

dtc/dtc-cyrus

dtc/dtc-postfix-courier

exim4

OK

OK

havp

OK

OK

libclamav-client-perl

OK

OK

linkchecker (suggests)

mahara

mailscanner

mimedefang

OK

OK

p3scan

OK

OK

pyclamd

OK

OK

MOTU/Clamav (last edited 2012-07-14 06:34:56 by kitterman)