Bug 1694098 - Update clamav to current version
Summary: Update clamav to current version
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: clamav
Version: el6
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Robert Scheck
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1765556 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-29 14:10 UTC by Fred Kienker
Modified: 2019-10-25 12:58 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-04-09 09:31:19 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Fred Kienker 2019-03-29 14:10:25 UTC 
Description of problem: Current EPEL version is out of date


Version-Release number of current component (if applicable): 0.101.1-1


Would it be possible to update the EPEL el6 clamav from version 0.101.1-1 to 0.101.2-1? This would bring it in line with the developers' current version. The 0.101.2-1 version is already released on EPEL for epel7.

Thanks!
Comment 1 Fedora Update System 2019-04-05 03:09:48 UTC 
clamav-0.100.3-1.el6 has been submitted as an update to Fedora EPEL 6. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-9c8cf7e4be
Comment 2 Fedora Update System 2019-04-09 01:03:47 UTC 
clamav-0.100.3-1.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.
Comment 3 Sergio Basto 2019-04-09 01:28:27 UTC 
Sorry el6 was not updated to 0.101 .
Comment 4 Robert Scheck 2019-04-09 09:31:19 UTC 
ClamAV was updated to the latest 0.100.x release, because updating to 0.101.x would lead to an ABI break. If really a ABI-breaking update is desired for EPEL 6 being close to EOL, this needs a separate bug report, but it also needs to be actually carried out by somebody else.
Comment 5 bunkobugsy 2019-10-25 12:58:55 UTC 
*** Bug 1765556 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.