Date: Tue, 24 Sep 2019 14:37:47 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 240794] security/suricata5: update to 5.0.0-rc1 and assorted port corrections Message-ID: <bug-240794-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D240794 Bug ID: 240794 Summary: security/suricata5: update to 5.0.0-rc1 and assorted port corrections Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: bofh@freebsd.org Reporter: franco@opnsense.org Assignee: bofh@freebsd.org Flags: maintainer-feedback?(bofh@freebsd.org) Created attachment 207772 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D207772&action= =3Dedit 5.0.0-rc1 Hello, security/suricata5 was created without ticket or discussion. I just found = it now and the state of the port is outdated and opportunistic at best. The n= ame "suricata5" is problematic because we want to update "suricata" to version 5 when that is out... A list of necessary changes: * Create a proper PYTHON option (align with security/suricata) * Set CONFLICTS_INSTALL properly (coexist with security/suricata) * GEOIP option here is broken based on outdated port option (align with security/suricata) * Add JSON option (align with security/suricata) * Add NETMAP option (align with security/suricata) * Disable HYPERSCAN default (align with security/suricata) * Fix outdated NSS option (align with security/suricata) * Fix outdated REDIS option (align with security/suricata) While here update to 5.0.0.rc1: https://suricata-ids.org/2019/09/24/please-help-us-test-suricata-5-0-0-rc1/ Cheers, Franco --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-240794-7788>