Currently I use Debian GNU/Linux 5.0 \n \l on one of my servers, in
production status. 64 bit. Running, among others server packages, the
following combo: clamav, freshclam, clamsmtpd, postfix, dovecot,
saslauth
When I do:
~# apt-get upgrade
I get:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages have been kept back:
squirrelmail
The following packages will be upgraded:
apache2 apache2-doc apache2-mpm-prefork apache2-suexec apache2-utils
apache2.2-common clamav clamav-base clamav-daemon clamav-freshclam
dhcp3-client dhcp3-common libclamav6
13 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Need to get 0B/27.7MB of archives.
After this operation, 373kB of additional disk space will be used.
Do you want to continue [Y/n]?
And after confirming that (Y) the process gets halted with some
warning about clamav-milter (which I don't even use a.f.a.i.k.):
Reading changelogs... Done
clamav (0.95.2+dfsg-1~volatile1) unstable; urgency=low
This release of clamav-milter requires you to amend your
configuration.
It's against the Debian volatile policy, but due to upstream
changes, we
decided that it was the best way forward, rather than maintaining an
outdated version.
Here is a summary of the required changes:
* clamav-milter configuration has been moved from
command-line options to the file /etc/clamav/clamav-milter.conf.
The
following is a map of commonly used options:
-l LocalNet
-o No longer needed/supported
-q No longer needed/supported
--noreject OnInfected (Blackhole|Accept|Quarantine)
--dont-wait No longer needed/supported
--max-children No longer needed/supported
* While at it, /etc/default/clamav-milter was reworked. If you've
previously
set $USE_POSTFIX in that file, please make sure to set the new
option
SOCKET_RWGROUP=postfix now.
Also, ensure that the MilterSocket setting in
/etc/clamav/clamav-milter.conf includes /var/spool/postfix, if you
are
using a chroot'ed smtpd instance (which is the default).
-- martin f. krafft <madduck.TakeThisOut@debian.org> Mon, 15 Jun 2009 08:20:10
+0200
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
(END)
So now I can only break the upgrade and have no clue what to do.
Pretty bad of clamav (and apt), to be honest, to leave the user
stranded like that. I've been testing on a separate machine, on which
I have tried to solve the exact same problem. Anyone know how to get
clam to be updated in Debian Lenny x64?
Thanks in advance for any and all info regarding this,
Nat
Linux