Bug 2040800
Summary: | Please update the epel8 version of suricata to 6.0.4 | ||
---|---|---|---|
Product: | [Fedora] Fedora EPEL | Reporter: | Davide Cavalca <davide> |
Component: | suricata | Assignee: | Steve Grubb <sgrubb> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | epel8 | CC: | ish, jmlich83, jtfas90, marco.rizzi.com, orion, sgrubb |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | suricata-6.0.9-1.el8 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2023-01-22 02:31:48 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Davide Cavalca
2022-01-14 18:01:03 UTC
I put up https://src.fedoraproject.org/rpms/suricata/pull-request/6 for this We usually try to keep our epel branches stable and not cause large, unexpected changes. After looking around, I see that epel8 is not up to date with the latest 5.x release. It will be pushed through the build system as a preliminary step. Suricata 5.0.X is now EOL. This should get updated to 6.0.X soon. FEDORA-EPEL-2023-2ec24bf8ea has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-2ec24bf8ea FEDORA-EPEL-2023-2ec24bf8ea has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-2ec24bf8ea See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2023-2ec24bf8ea has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report. |