[users] Issue with new clamav package

[Kai Schaetzl]

Hi folks!

I just installed the new clamav package 0.97.5-2.el5.rf and found that it
stopped clamd on the two systems I installed it.
The reason are these null files, specifically the main.cld, which throws
an error "Broken or not a CVD file" to the logs.
-rw-r--r-- 1 clamav clamav 0 Jun 25 11:19 daily.cld.rpmnew
-rw-r--r-- 1 clamav clamav 0 Jun 25 11:19 main.cld
Remove these files and you can restart clamd just fine.

From reading the recent thread "new rpm clamav 0.97.5" I gather that this

happened because of the missing database files in the source and Dag
accidentally not removing the filesystem references to them in the spec
file when rushing this package out.

It's a good thing that the database files are gone now as they were just
interfering with the already downloaded local files. So, I would think
that those references just have to get completely removed and the next
update is good for keeping clamd online.

Kai

[Kai Schaetzl]

Hi folks!

I just installed the new clamav package 0.97.5-2.el5.rf and found that it
stopped clamd on the two systems I installed it.
The reason are these null files, specifically the main.cld, which throws
an error "Broken or not a CVD file" to the logs.
-rw-r--r-- 1 clamav clamav 0 Jun 25 11:19 daily.cld.rpmnew
-rw-r--r-- 1 clamav clamav 0 Jun 25 11:19 main.cld
Remove these files and you can restart clamd just fine.

From reading the recent thread "new rpm clamav 0.97.5" I gather that this

happened because of the missing database files in the source and Dag
accidentally not removing the filesystem references to them in the spec
file when rushing this package out.

It's a good thing that the database files are gone now as they were just
interfering with the already downloaded local files. So, I would think
that those references just have to get completely removed and the next
update is good for keeping clamd online.

Kai