[Pkg-clamav-devel] [Fwd: Recent clamav-milter upgrade from volatile broken]

[Michael Tautschnig]

[...]
> 
> So I will have to change a really well working email system without any
> reason. Changing configurations wouldn't have been a problem. Removing
> functionality without providing alternatives is. None of the alternative
> solutions recommended by the clamav folks are in any way that simple and
> easy to setup than the clamav-milter was.
> 
> Whatsoever, this is nothing debian specific so thanks a lot for helping
> me. Waiting 20 months for the debian distribution to stabilize and the
> first upgrade breaks the system. Should have been a dist-upgrade then.
> There really is no need for debian if things are going that road now. It
> were the great debian packages decoupling the distribution from any
> upstream insanity I chose it for.
> 

Well, you're using volatile. Using volatile will always give you a bit of a
dist-upgrade (which is intentional - you chose to go with volatile to get the
latest and greatest, which it unfortunately wasn't for you usecase).

You've got to choose: Somewhat older clamav stuff (0.94 + security upgrades) or
the latest upstream, via volatile. Upstream has chosen to rewrite clamav-milter
in a minimalistic way. There is nothing that we as the Debian package
maintainers of clamav can do about it in any reasonable way, especially with the
lack of knowledge that the now dropped features were so much required. It should
be noted that, thus far, you're the only one telling the pkg-clamav team that
this is the typical usecase. We'll likely need to put something about these
missing features in the upgrade notes of squeeze, but upstream may also decide
to re-add those features until the release of squeeze, we don't know.

> Btw, the clamav upgrade really brought a /etc/default/clamav-milter file
> with it. This new file contains the line
> 
> RESTART_AFTER_CLAMD=yes
> 
> and as soon as this is set to yes, clamav-milter cannot be started
> anymore stating a warning that clamd may be needed and that it will be
> started by clamd. clamav-milter will not be started by clamd for me.
> 

No, it should cause clamav-milter to be RE-started in case clamd is upgraded. It
should not stop anything from being started. If it does, please copy&paste the
error message here.

Best,
Michael

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 194 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-clamav-devel/attachments/20090430/a7e5162d/attachment.pgp>