From: Michael Tremer <michael.tremer@ipfire.org>
To: Matthias Fischer <matthias.fischer@ipfire.org>
Cc: development@lists.ipfire.org
Subject: Re: [PATCH] suricata: Update to 7.0.10
Date: Wed, 26 Mar 2025 10:10:16 +0000 [thread overview]
Message-ID: <A1D723AC-9004-4750-99D2-2634421932FA@ipfire.org> (raw)
In-Reply-To: <20250325180854.3288744-1-matthias.fischer@ipfire.org>
Thank you. Merged!
> On 25 Mar 2025, at 18:08, Matthias Fischer <matthias.fischer@ipfire.org> wrote:
>
> For details see:
> https://suricata.io/2025/03/25/suricata-7-0-10-released/
>
> "This is an extra release to address a critical issue in 7.0.9 affecting
> AF_PACKET users: setting a BPF would cause Suricata to fail to start up. As
> this affected many users, we’ve decided to push this release earlier than
> originally planned. Our QA processes have been updated to avoid similar
> issues going forward."
>
> Signed-off-by: Matthias Fischer <matthias.fischer@ipfire.org>
> ---
> lfs/suricata | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/lfs/suricata b/lfs/suricata
> index 56733125d..0b0de5654 100644
> --- a/lfs/suricata
> +++ b/lfs/suricata
> @@ -24,7 +24,7 @@
>
> include Config
>
> -VER = 7.0.9
> +VER = 7.0.10
>
> THISAPP = suricata-$(VER)
> DL_FILE = $(THISAPP).tar.gz
> @@ -40,7 +40,7 @@ objects = $(DL_FILE)
>
> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>
> -$(DL_FILE)_BLAKE2 = fe01a304b170cf210b3ad2c782c6a49798c67df5433498715101ba626548395a70793a50221390f6697d1aef2be1808ba430091dae097e350dd2a9c98677a61b
> +$(DL_FILE)_BLAKE2 = c33e3ccf0e5298f3548747a3d9bc52662cf97caa775a4f7e3689fe4bc95d2ad9269d344c67654ad6e03fe463054052bb5d5e720bc67040cb179b041cdb0423d2
>
> install : $(TARGET)
>
> --
> 2.43.0
>
>
prev parent reply other threads:[~2025-03-26 10:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 18:08 Matthias Fischer
2025-03-26 10:10 ` Michael Tremer [this message]
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=A1D723AC-9004-4750-99D2-2634421932FA@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
--cc=matthias.fischer@ipfire.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