Upgrade ClamAV from 0.96.5 to 0.97.2

7 posts / 0 new
Last post
#1 Tue, 09/13/2011 - 09:11

Upgrade ClamAV from 0.96.5 to 0.97.2

Until recently, I was able to upgrade ClamAV by following the advice here http://ubuntuforums.org/showpost.php?p=9882970&postcount=2 , but now find I get a message like "no trusted key found" when applying apt-key adv etc...

I have since discovered that ClamAV can be upgraded to 0.97.2 by simply un-commenting the backport entries in /etc/apt/sources.list and following the usual apt-get update/upgrade procedure, but I notice the following upgrades are also available:- language-selector-common postfix postfix-pcre (upgrades postfix from 2.7.0 to 2.8.1).

Is it safe to apply the postfix upgrade, or is it likely to 'break things' in Webmin?

Thanks for any advice.

Tue, 09/13/2011 - 09:31


Well, the only things we know for sure are that the package versions included in the stock distro will work fine :-)

I would be surprised if any syntax changed so drastically in Postfix 2.8 that it broke your config or Webmin, but we haven't tested upgrading to that.

Unless there's really something in that version that you need, or it's okay if your server experiences some downtime, I'd recommend not making changes to your standard distro-supplied packages.

So, it'd be my recommendation to not try upgrading Postfix :-)


Tue, 09/13/2011 - 09:50

Thanks for the prompt reply Eric.

In no hurry to upgrade postfix.

Please excuse my ignorance, but does the same philosophy also apply to upgrading language-selector-common, or is it ok to go ahead with that?

Tue, 09/13/2011 - 10:06

Well, every change you make from the default vendor supplied packages for your distro comes with a risk.

I think ClamAV is a reasonable change, but I don't think I'd pull in any other packages from backports unless you can point to the new features provided by that package and say "I really need that!".

So, it would be my suggestion to not pull in language-selector-common from the backports repository :-)


Mon, 10/03/2011 - 09:31

I'm trying to do the uninstall of the ClamAV from RPMForge and going to the virtualmin supplied one (since I'm getting the same error). However, it's asking to remove the virtualmin base package. Not wanting to proceed like an idiot, I need some guidance on how to work around this. I'm not attached to RPMForge.


Package Arch Version Repository Size

Removing: clamd x86_64 0.97.2-1.el5.rf installed 576 k Removing for dependencies: virtualmin-base noarch 1.0-61.rh installed 0.0

Transaction Summary

Remove 2 Package(s) Reinstall 0 Package(s) Downgrade 0 Package(s)

Tue, 10/04/2011 - 08:45

Yeah, the virtualmin-base package depends on ClamAV, so you would indeed get a message such as you're seeing.

You could always delete the ClamAV packages with RPM's "--nodeps" flag, which will tell it to ignore any dependencies.

Then, disable the RPMForge repo, and then install the Virtualmin ClamAV packages when you're done.


Thu, 03/21/2013 - 10:37
Topic locked