[Bug 571543] Re: Milter and Freshclam configurations buggy in Lucid

[Imre Gergely]

I've managed to reproduce the last problem too. It only appears when
upgrading from 1ubuntu2 to 2ubuntu1 (from RC to release). After that
another update to -proposed fixes it. There's a small problem though as
far as I can tell. Consider the following:

- somebody upgraded to Lucid -rc
- installed clamav with freshclam. Default NotifyClamd is set to 'Yes'
- upgraded to Lucid release (clamav 1ubuntu2) after release day, NotifyClamd gets invalidated (actually right now it's set to not notify clamd)
- now he upgrades to this package from -proposed, problem gets fixed but option stays on 'No', so there will be no clamd notifications from now on.

I also checked the other scenario:

- somebody upgraded to Lucid -rc
- installed clamav with freshclam. Default NotifyClamd is set to 'Yes'. He sets it to 'No', thus disabling the notification by choise
- upgraded to Lucid release (clamav 1ubuntu2) after release day, NotifyClamd DOES NOT get invalidated (config.dat is still on 'false' and not 'path')
- now he upgrades to this package from -proposed, there's nothing to fix, but the option is still on 'No' (which he had initially)

I conclude that: if 'path' is present at value it means that there was
'true' before, so it needs to be 'true' after upgrade also.

-- 
Milter and Freshclam configurations buggy in Lucid
https://bugs.launchpad.net/bugs/571543
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to clamav in ubuntu.