Description of problem: # file /var/lib/clamav/daily.cvd /var/lib/clamav/daily.cvd: Clam AntiVirus database 08 Jan 2018 16-17 -0500, version2420, gzipped But the header of the file is: ClamAV-VDB:08 Jan 2018 16-17 -0500:24204:1820280:63:581a1410813ce37d1b6ee123b7f2e8ca:kH1EdruJV9T90+8H7HlRfppjd99Qfh0zQq2EUMPtSabQU9mdsnPO7IbYRAYO1EN+ALbkey873vrD4N8vTy7p8tjGW7268pBbZde5Lj0PvyDKuiByJ7pXdeCPndaPCAjIOirrfSqL3G7fqt1+Rtv5ITCS8vcQr3+jAfLnbEnUiU:neo:1515446246 Indicating that the version is 24204. Also, there used to be a space between "version" and the number: Clam AntiVirus database 26 Jan 2018 04-24 -0500, version 2425, gzipped Version-Release number of selected component (if applicable): file-5.32-1.fc28.x86_64 I would have reported upstream, but gw.com does not appear to be responding.
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle. Changing version to '28'.
(In reply to Orion Poplawski from comment #0) > Description of problem: > > # file /var/lib/clamav/daily.cvd I do not have access to such a file, so it is difficult to debug for me. > I would have reported upstream, but gw.com does not appear to be responding. It is a known issue. Please try to contact the upstream maintainer directly: christos <at> zoulas <dot> com
(In reply to Kamil Dudka from comment #2) > (In reply to Orion Poplawski from comment #0) > > Description of problem: > > > > # file /var/lib/clamav/daily.cvd > > I do not have access to such a file, so it is difficult to debug for me. > > > I would have reported upstream, but gw.com does not appear to be responding. > > It is a known issue. Please try to contact the upstream maintainer directly: > > christos <at> zoulas <dot> com the files in question : http://database.clamav.net/main.cvd http://database.clamav.net/daily.cvd http://database.clamav.net/bytecode.cvd
Thanks! I have posted the below patch to the upstream maintainer.
Created attachment 1459126 [details] [PATCH] magic: support longer version strings for clamav database ... and remember to put a space between "version" and the number This approach is likely not going to scale in long term but I am not sure how to encode the version number parsing in a better way.
upstream commit: https://github.com/file/file/commit/1a7f58c9
file-5.33-7.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-79bf4a4890
file-5.33-7.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-79bf4a4890
file-5.33-7.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.