Koozali.org: home of the SME Server

Obsolete Releases => SME 7.x Contribs => Topic started by: steve288 on April 26, 2007, 09:55:35 PM

Title: Why doesnt clamav update ??
Post by: steve288 on April 26, 2007, 09:55:35 PM
My logs says that my clam is outdated.
WARNING: Local version: 0.90.1 Recommended version: 0.90.2

I try typing "yum upgrade clamav" but it says ;
.......
Could not find update match for clamav
No Packages marked for Update/Obsoletion
================================================================
No new rpms were installed. No additional commands are required.
================================================================

I tryed yum update and that says
"No new rpms were installed. No additional commands are required."

What Am I doing wrong ??

Regards




-- error message in  logfile
Current working dir is /var/clamav
Max retries == 6
ClamAV update process started at Mon Apr 23 04:08:20 2007
Querying current.cvd.clamav.net
TTL: 900
Software version from DNS: 0.90.2
WARNING: Your ClamAV installation is OUTDATED!
WARNING: Local version: 0.90.1 Recommended version: 0.90.2
DON'T PANIC! Read http://www.clamav.net/support/faq
main.cvd version from DNS: 43
main.cvd is up to date (version: 43, sigs: 104500, f-level: 14, builder: sven)
daily.cvd version from DNS: 3150
daily.inc is up to date (version: 3150, sigs: 6694, f-level: 15, builder: ccordes)
Title: Re: Why doesnt clamav update ??
Post by: dmay on April 26, 2007, 11:48:35 PM
Quote from: "steve288"
I try typing "yum upgrade clamav" but it says...

Because 0.90.2 has not moved into the smeupdates repository. It currently resides in the smetest repository. At your own risk, you may do the following:

# yum upgrade clamav clamav-db clamd smeserver-clamav --enablerepo=smetest

Darrell
Title: Why doesnt clamav update ??
Post by: steve288 on April 27, 2007, 03:07:05 PM
Thanks thats helpfully.

Im sure that you cant answer this but IM just wondering out loud. Why the warning message would be someone false or at least confusing. In that its saying we should upgrade when this is not really a fully tested version.

Thank you.
Title: Why doesnt clamav update ??
Post by: okepc on April 27, 2007, 03:15:36 PM
In fact clamav tells you that there is a newer version.
The dev team of smeserver needs to build and test clamav to make sure everything is working perfectly before they release it to the public.
Thats why it is in the testing repository.
The sme team are NOT the clamav developers but in fact the packagers.

So smeserver is build on a compilation of different software developed by other developers, the sme developers put it all together so it works seamlessly.

Dirk
Title: Why doesnt clamav update ??
Post by: Stefano on April 27, 2007, 03:34:59 PM
Quote from: "steve288"
Thanks thats helpfully.

Im sure that you cant answer this but IM just wondering out loud. Why the warning message would be someone false or at least confusing. In that its saying we should upgrade when this is not really a fully tested version.

Thank you.


'cause that message comes from clamav and not from SME..

btw, it says

Quote

WARNING: Local version: 0.90.1 Recommended version: 0.90.2
DON'T PANIC! Read http://www.clamav.net/support/faq


if you have a spare machine or a virtual one for testing purposes, you could help dev team to test new clamav release ;-)

ciao

Stefano
Title: Why doesnt clamav update ??
Post by: compdoc on May 27, 2007, 05:03:16 PM
Ive been getting the 'WARNING: Your ClamAV installation is OUTDATED!' on a few SME servers for some time. Any idea when they'll release it?
Title: Why doesnt clamav update ??
Post by: Stefano on May 27, 2007, 05:23:07 PM
Quote from: "compdoc"
Ive been getting the 'WARNING: Your ClamAV installation is OUTDATED!' on a few SME servers for some time. Any idea when they'll release it?


when all the clamav rpm will be tested..

if you want, you can help dev team..

Ciao
Stefano
Title: Why doesnt clamav update ??
Post by: christian on May 27, 2007, 06:06:40 PM
Searching in bugzilla leads to a rather long thread of the sme dev team attempting to isolate an issue in 0.90.1 which is affecting a number of people. Moving to 0.90.2 in some cases was exacerbating the problem. So I expect they are trying to isolate the root cause and potentially get it fixed upstream before moving forward.