Re: Future of ClamAV on EPEL ?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 3/7/23 13:48, Stephen Smoogen wrote:


On Tue, 7 Mar 2023 at 15:00, Andrew C Aitchison <andrew@xxxxxxxxxxxxxxx <mailto:andrew@xxxxxxxxxxxxxxx>> wrote:


    This question is prompted by a question from kumar bava about EPEL7
    on the ClamaAV Users list:
    https://lists.clamav.net/pipermail/clamav-users/2023-March/013338.html <https://lists.clamav.net/pipermail/clamav-users/2023-March/013338.html>

    EPEL currently ship the anti-virus ClamAV v0.103.8

     From September ClamAV 0.103 will be EOL, and all
    supported versions will require Rust.

    Rust is available on RHEL 7, 8 and 9 as a part of Red Hat Developer
    Tools.
    Does that mean that EPEL will or will not be able to continue packaging
    ClamAV ?

    ClamAV do provide rpms, so it may not be the end of the world if
    ClamAV disappears from EPEL, but the details of the packing,
    especially config locations and defaults may be different.


EPEL packages are maintained by volunteers who 'shephard' a particular package for as long as the volunteer can do so. I have cc'd the main ones I have seen making commits and builds in case they aren't following the epel-devel list closely.

That said, EL7 will only be around til June 2024. There will only be so much 'heavy-lifting' possible to keep things going in that time-frame

I've been looking into things and I think we will be able to update clamav in EL7 and EL8 to 1.0.X once 0.103.X goes EOL. We're basically just waiting on one issue to get resolved at the moment:

https://github.com/Cisco-Talos/clamav/issues/842

--
Orion Poplawski
he/him/his  - surely the least important thing about me
IT Systems Manager                         720-772-5637
NWRA, Boulder/CoRA Office             FAX: 303-415-9702
3380 Mitchell Lane                       orion@xxxxxxxx
Boulder, CO 80301                 https://www.nwra.com/

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

_______________________________________________
epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Index of Archives]     [Fedora Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Announce]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Linux Apps]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Fedora ARM]

  Powered by Linux