All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aaron Mestdagh <a.mestdagh3@gmail.com>
To: buildroot@buildroot.org
Cc: Thomas Devoogdt <thomas@devoogdt.com>, Aaron <aaron.mestdagh@barco.com>
Subject: [Buildroot] [PATCH 4/4] package/fluent-bit: bump fluent-bit to 5.1.2
Date: Thu, 22 Oct 2026 18:42:12 +0200	[thread overview]
Message-ID: <20261022164212.615-1-a.mestdagh3@gmail.com> (raw)

From: Aaron <aaron.mestdagh@barco.com>

Upgrade from 4.2.0 to 5.1.2, bringing multi-worker network ingestion
and improved OpenTelemetry processing.

The 5.x releases also add Google Cloud Storage output, Windows Event
Tracing input, NVIDIA GPU metrics, and new metrics processors, alongside
FIPS, TLS, and proxy improvements.

Signed-off-by: Aaron <aaron.mestdagh@barco.com>
---
 ...001-ripser-initialize-temporary-entry.patch | 18 ++++++++++++++++++
 package/fluent-bit/fluent-bit.hash             |  2 +-
 package/fluent-bit/fluent-bit.mk               |  2 +-
 3 files changed, 20 insertions(+), 2 deletions(-)
 create mode 100644 package/fluent-bit/0001-ripser-initialize-temporary-entry.patch

diff --git a/package/fluent-bit/0001-ripser-initialize-temporary-entry.patch b/package/fluent-bit/0001-ripser-initialize-temporary-entry.patch
new file mode 100644
index 0000000000..c98bce88a9
--- /dev/null
+++ b/package/fluent-bit/0001-ripser-initialize-temporary-entry.patch
@@ -0,0 +1,18 @@
+From: Buildroot package compatibility
+Subject: [PATCH] ripser: initialize temporary diameter entry
+Upstream: https://github.com/Ripser/ripser
+
+GCC 6 does not accept the implicit default construction of
+diameter_entry_t. The temporary is assigned before it is used, so initialize
+it with Ripser's existing invalid-index sentinel.
+
+Upstream-Status: Pending (https://github.com/fluent/fluent-bit/pull/12533)
+
+Signed-off-by: Aaron <aaron.mestdagh@barco.com>
+diff --git a/lib/ripser-1.2.1/ripser.cpp b/lib/ripser-1.2.1/ripser.cpp
+--- a/lib/ripser-1.2.1/ripser.cpp
++++ b/lib/ripser-1.2.1/ripser.cpp
+@@ -185,0 +186,1 @@
++	diameter_entry_t() : std::pair<value_t, entry_t>() {}
+-- 
+2.43.0
diff --git a/package/fluent-bit/fluent-bit.hash b/package/fluent-bit/fluent-bit.hash
index be02761ed5..7fb94d60b2 100644
--- a/package/fluent-bit/fluent-bit.hash
+++ b/package/fluent-bit/fluent-bit.hash
@@ -1,3 +1,3 @@
 # Locally computed
-sha256  44fe0f52e89a63b213695748f99691d0a6247a4bd05065f1b517c798d9f89bcc  fluent-bit-4.2.0.tar.gz
+sha256  1971d86c7dc0f3e6b906890297635d6a3a84e5e7ad64d36521b74da202fda62f  fluent-bit-5.1.2.tar.gz
 sha256  0d542e0c8804e39aa7f37eb00da5a762149dc682d7829451287e11b938e94594  LICENSE
diff --git a/package/fluent-bit/fluent-bit.mk b/package/fluent-bit/fluent-bit.mk
index a3a44b8dbe..b53da90706 100644
--- a/package/fluent-bit/fluent-bit.mk
+++ b/package/fluent-bit/fluent-bit.mk
@@ -4,7 +4,7 @@
 #
 ################################################################################
 
-FLUENT_BIT_VERSION = 4.2.0
+FLUENT_BIT_VERSION = 5.1.2
 FLUENT_BIT_SITE = $(call github,fluent,fluent-bit,v$(FLUENT_BIT_VERSION))
 FLUENT_BIT_LICENSE = Apache-2.0
 FLUENT_BIT_LICENSE_FILES = LICENSE
-- 
2.43.0

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

             reply	other threads:[~2026-10-22 16:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-22 16:42 Aaron Mestdagh [this message]
2026-10-22 21:03 ` [Buildroot] [PATCH 4/4] package/fluent-bit: bump fluent-bit to 5.1.2 Thomas Petazzoni via buildroot
2026-10-22 21:12   ` Thomas Devoogdt
2026-10-24 19:03     ` [Buildroot] [PATCH v2] " Thomas Devoogdt
2026-10-24 21:10       ` Thomas Petazzoni via buildroot

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=20261022164212.615-1-a.mestdagh3@gmail.com \
    --to=a.mestdagh3@gmail.com \
    --cc=aaron.mestdagh@barco.com \
    --cc=buildroot@buildroot.org \
    --cc=thomas@devoogdt.com \
    /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.