All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernd Kuhls <bernd@kuhls.net>
To: buildroot@uclibc.org
Subject: Re: [Buildroot] [PATCH 1/1] package/suricata: bump version to 8.0.4
Date: Mon, 06 Apr 2026 20:39:49 +0200	[thread overview]
Message-ID: <pan$7060f$23e99787$e312250a$d96db09d@ID-313208.user.individual.net> (raw)
In-Reply-To: 9bd76f389facb56a8418edbee7d9fe8f__43245.0398498744$1775462663$gmane$org@free.fr

Hi Julien,

Am Mon, 06 Apr 2026 10:03:55 +0200 schrieb Julien Olivain via buildroot:

> I did not checked when those CVEs were introduced or if they are
> all applicable, but this should be mentioned in the commit log.
> It is likely this bump should be marked as a "security" one.

done:
https://patchwork.ozlabs.org/project/buildroot/patch/
20260406181810.1853090-1-bernd@kuhls.net/

> I believe your first motivation was to get rid of pcre (v1)
> dependency

Yes, sent the next batch of patches:
https://patchwork.ozlabs.org/project/buildroot/list/?series=498885

For Kodi and Freeswitch I am testing backported patches and will send them 
later.

Afaics the only package where I could not find pcre2 support is the 2.x 
branch of snort. Debian for example removed snort2 in 2024:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079286

Since we have snort3 we should also remove snort 2.x.

@Sergio: You are the maintainer of the buildroot package. What do you 
think?

Regards, Bernd

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2026-04-06 18:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-03 19:12 [Buildroot] [PATCH 1/1] package/suricata: bump version to 8.0.4 Bernd Kuhls
2026-04-06  8:03 ` Julien Olivain via buildroot
     [not found] ` <9bd76f389facb56a8418edbee7d9fe8f__43245.0398498744$1775462663$gmane$org@free.fr>
2026-04-06 18:39   ` Bernd Kuhls [this message]
2026-04-06 23:47     ` Sergio Prado

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='pan$7060f$23e99787$e312250a$d96db09d@ID-313208.user.individual.net' \
    --to=bernd@kuhls.net \
    --cc=buildroot@uclibc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.