public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Jason Taylor <jtfas90@proton.me>
To: git-commits@fedoraproject.org
Subject: [rpms/suricata] epel10: Upstream security/bugfix release
Date: Thu, 04 Jun 2026 04:11:40 GMT [thread overview]
Message-ID: <178054630037.1.12279353931911059067.rpms-suricata-9cc326e40fcb@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/suricata
Branch : epel10
Commit : 9cc326e40fcb0c46646b6a959af24883aa9103a2
Author : Jason Taylor <jtfas90@proton.me>
Date : 2026-03-18T23:41:32-04:00
Stats : +6/-2 in 3 file(s)
URL : https://src.fedoraproject.org/rpms/suricata/c/9cc326e40fcb0c46646b6a959af24883aa9103a2?branch=epel10
Log:
Upstream security/bugfix release
---
diff --git a/.gitignore b/.gitignore
index 8de572a..377755a 100644
--- a/.gitignore
+++ b/.gitignore
@@ -95,3 +95,4 @@ suricata-1.0.0.tar.gz.sig
/suricata-7.0.11.tar.gz
/suricata-8.0.1.tar.gz
/suricata-8.0.2.tar.gz
+/suricata-8.0.3.tar.gz
diff --git a/sources b/sources
index 2f70401..0af2d59 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (suricata-8.0.2.tar.gz) = 842c6aac70099500a0c82a6ca9e01cb9cd14652060e2c492b7df234f053116595dc9ead12c184982deed0afe2990f3fd1b7ef939475fdaff63e0727bba1dd313
+SHA512 (suricata-8.0.3.tar.gz) = 2b8fc6416fb001d073a66ee9a14bab7825aee6dcecc44019a28d20b6e06d802a85f0ec37be118ef0a8f787d7b0e4e37eedb08df915ba010fb72fb2176127af40
diff --git a/suricata.spec b/suricata.spec
index 0996aed..fb77c8d 100644
--- a/suricata.spec
+++ b/suricata.spec
@@ -1,6 +1,6 @@
Summary: Intrusion Detection System
Name: suricata
-Version: 8.0.2
+Version: 8.0.3
Release: 1%{?dist}
License: GPL-2.0-only
URL: https://suricata.io/
@@ -195,6 +195,9 @@ fi
%endif
%changelog
+* Wed Mar 18 2026 Jason Taylor <jtfas90@proton.me> 8.0.3-1
+- Upstream security/bugfix release
+
* Sat Nov 08 2025 Jason Taylor <jtfas90@proton.me> 8.0.2-1
- Upstream security/bugfix release
reply other threads:[~2026-06-04 4:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=178054630037.1.12279353931911059067.rpms-suricata-9cc326e40fcb@fedoraproject.org \
--to=jtfas90@proton.me \
--cc=git-commits@fedoraproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox