Red Hat Bugzilla – Bug 164734
clamav in FC2 repo has fc1 disttag
Last modified: 2007-11-30 17:11:10 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows 98; Win 9x 4.90; H010818)
Description of problem:
The clamav RPMs in the FC2 repository at fedora.us have "fc1" disttags. I haven't checked whether these are the wrong packages or whether they only have a wrong disttag, but either way something is messed up.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Just look at the disttag. ;-)
Actual Results: There is an "fc1" disttag.
Expected Results: There should be an "fc2" disttag.
My fault, I will fix this soon.
Kevin, please help by verifying that the packages here work properly.
I fetched the updated clamav, clamav-data, clamav-lib and clamav-update RPMs
from the pending URL you mentioned onto my FC2 system (they installed fine) and:
* ran freshclam. It told me to edit the example freshclam.conf. (This has
changed between the very old clamav packages previously in FC2 and the new
ones. Upstream decided that the default freshclam.conf is not good enough
because you should select a mirror for your country rather than just using a
random one. FC3/FC4 went through this change earlier.) I complied and did the 2-
* ran freshclam again. Worked fine.
* ran clamscan on a known clean directory. Worked fine.
* ran clamscan on the EICAR antivirus test file. Detected the "virus" just fine.
I didn't test the milter because I don't have a mailserver running here (just a
laptop still running FC2 because I didn't get around to updating it to a newer
Actually, the freshclam.conf stuff was already in the previous update (0.85), I
guess. I probably just hadn't run freshclam since then. ;-)
Why are these still pending? They fix the disttag issue in the released
packages and I honestly can't see what they could break.
FC2 is discontinued even by Legacy now, so I don't expect this to get fixed