is it possible to build suricata for EPEL, to make it available on RHEL6?
Created attachment 951843 [details]
Patch to build for epel-7.
Here is a patch that enables the f20 to build for epel-7. The only change is to not use luajit, and just use liblua support instead.
Additionally, copytruncate is no longer required.
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 20 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.
Could this bug be reopened? Suricata is still not available for epel. It would be awesome to have it on both, epel 6 and 7.
If possible I'd like to help out here. I'm currently part of the Suricata core team and do maintain EL7 Suricata RPMs (based on these Fedora ones) in an external repository and on copr.
There is a change that I would like to make before pushing it out into EPEL. Currently it runs as root, which is bad. I'd like to change it to run on a "suricata" account. That means fixing file permissions in the rpm specfile. I'd also like to push the same thing into rawhide so that its corrected on Fedora some day. If anyone has time to fix the spec file and attach a patch, I'll take care of the rest. Otherwise I'll see if I can find some spare time to play with this next month. Thanks.
Created attachment 1122850 [details]
I'm attaching .spec file patch to run suricata under suricata user. I also see, that there is now stable suricata 3.0 release. Do you want to help with rebase as well? It would be great to have 3.0 in epel.
Thanks. I'll look at the patch next week when I get back from DevConf. I already have another patch moving to 3.0. I'll combine them both for rawhide/F24/EPEL7 and just use the other patch for F23/22. Thanks again for the patch.
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle.
Changing version to '24'.
More information and reason for this action is here:
Patch has been applied and new build pushed into rawhide.
suricata-3.0-1.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-59d44f4fd2
suricata-3.0-1.el7 has been pushed to the Fedora EPEL 7 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-EPEL-2016-59d44f4fd2
suricata-3.0-1.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.