ClamAV Upgrade


I was wondering when will there ever be an upgrade to a more recent ClamAV from the virtualmin repo?

For the longest time now I’ve been using an outdated version:

WARNING: Your ClamAV installation is OUTDATED!
WARNING: Local version: 0.98.5 Recommended version: 0.99.1

I can get from another repo but since the ClamAV on my system is from the virtualmin repo, I would like to not mix up packages etc. Besides the ClamAV that comes from the virtualmin repo is specifically configured for virtualmin/webmin I believe…

Any news on this would be great. Thanks.


What distro/version is it that you’re using there?


Hello Eric,

My distro/version is: CentOS Linux 6.7

Webmin version: 1.791

(I know you didn’t ask but I can’t seem to find the Virtualmin version info anywhere. I was going to post that too here for your reference incase of anything)

Any update on this? :slight_smile:

Well anyone else using an old version of Clamav and don’t get any upgrade from virtualmin repo?

I’m using Virtualmin version 5.01.gpl on Ubuntu Linux 14.04.1 and my Clamav is Local version: 0.98.7 Recommended version: 0.99.1
I’d feel better having my software updated but after a bad experience updating fail2ban manually, I’m going to wait til an official repo version comes down the pipes. That’s not Virtualmin’s fault, it’s just what we get for Ubuntu.
Btw, I wasn’t getting virus definition updates for a looooong time until I scheduled a periodic cronjob to run freshclam. I’d expected Virtualmin would set that up automatically.

I see, thanks for the response. I’m on Centos and I too was waiting for my distro to release an update for clamav for a long time and saw that it wasn’t happening. So then I went and checked what repo my clamav came from and it’s virtualmin. So I am assuming that’s where the update will come from and also I read/heard that it’s best to keep your installed packages from the same repo if you ever update/upgrade your packages. For example, once I got an update for httpd (apache) from my distro and thought "ah cool, time to update… " so I did and it completely messed up my sites. After reinstall/installing the httpd from virtualmin, everything went back to normal.

In my opinion and experience thus far, any packages related to virtualmin functioning properly etc, make sure you do updates from the virtualmin repo instead of another repo that has the same package to be updated. For example, I can activate the epel repo on my system and I get updates for clamav, httpd, etc, but I choose not to update from that because it may effect how virtualmin works on the system, as explained above about httpd for example. I may be wrong, but I think the packages contained in the virtualmin repo are specifically configured for your virtualmin to work properly. That is why I do not update my clamav from epel repo because it may effect how virtualmin uses clamav to properly work for your sites, etc.

For my system, I have just the distro repo’s enabled along with virtuallmin. Third party repo’s like epel, are okay if you need to grab something unrelated to virtualmin’s functionality but other than that, I have it disabled.

I am using 0.99.1-1.el7 and i was updated from epel and virtualmin. YUM is smart to check for dependency and it keeps on setting a priority list for updates. If most of the file was from virtualmin repo, it won’t touch the “outdated” package if it will come from epel.

Just saw you are using Ubuntu, no idea how the packager/updater works in ubuntu. I stop using ubuntu as soon as I realize I can work better(and locked out alot) with Fedora