From: devin.buildroot@gmail.com
To: buildroot@buildroot.org
Cc: Philippe Proulx <eeppeliteloop@gmail.com>,
Devin Steffler <devin.buildroot@gmail.com>
Subject: [Buildroot] [PATCH 2/3] package/lttng-tools: bump to version 2.13.14
Date: Sat, 22 Feb 2025 08:31:26 -0500 [thread overview]
Message-ID: <20250222133127.9445-2-devin.buildroot@gmail.com> (raw)
In-Reply-To: <20250222133127.9445-1-devin.buildroot@gmail.com>
From: Devin Steffler <devin.buildroot@gmail.com>
This is the second of three patches relating to lttng-modules 2.13.10 not compiling with buildroot.
Since I am submitting a patch to bump lttng-modules to 2.13.17 and lttng-tools is a tightly related package,
I am also submitting this patch to bump lttng-tools to 2.13.14 (the latest version at this time).
The chanagelog for lttng-tools 2.13.14 can be found here:
https://git.lttng.org/?p=lttng-tools.git;a=blob_plain;f=ChangeLog;hb=556250037f05705059581107159a60c2c7468744
Signed-off-by: Devin Steffler <devin.buildroot@gmail.com>
---
package/lttng-tools/lttng-tools.hash | 4 ++--
package/lttng-tools/lttng-tools.mk | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/package/lttng-tools/lttng-tools.hash b/package/lttng-tools/lttng-tools.hash
index b48904d0b9..c280809666 100644
--- a/package/lttng-tools/lttng-tools.hash
+++ b/package/lttng-tools/lttng-tools.hash
@@ -1,5 +1,5 @@
-# From https://lttng.org/files/lttng-tools/lttng-tools-2.13.8.tar.bz2.sha256
-sha256 b1e959579b260790930b20f3c7aa7cefb8a40e0de80d4a777c2bf78c6b353dc1 lttng-tools-2.13.8.tar.bz2
+# From https://lttng.org/files/lttng-tools/lttng-tools-2.13.14.tar.bz2.sha256
+sha256 53bdf7c4ad07dbfe660ee4d9affc63fe44ae59e9a73c6f7a96e0fca140e5adcb lttng-tools-2.13.14.tar.bz2
# Locally computed
sha256 068e55c7dbe597400199aee75ac5e71bdb2ca88c4c9a4cfa8e1fbc61f933eda5 LICENSE
diff --git a/package/lttng-tools/lttng-tools.mk b/package/lttng-tools/lttng-tools.mk
index add1f12a8c..5a1e555f7a 100644
--- a/package/lttng-tools/lttng-tools.mk
+++ b/package/lttng-tools/lttng-tools.mk
@@ -4,7 +4,7 @@
#
################################################################################
-LTTNG_TOOLS_VERSION = 2.13.8
+LTTNG_TOOLS_VERSION = 2.13.14
LTTNG_TOOLS_SITE = https://lttng.org/files/lttng-tools
LTTNG_TOOLS_SOURCE = lttng-tools-$(LTTNG_TOOLS_VERSION).tar.bz2
LTTNG_TOOLS_INSTALL_STAGING = YES
--
2.43.0
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-02-22 13:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-22 13:31 [Buildroot] [PATCH 1/3] package/lttng-modules: bump to version 2.13.17 devin.buildroot
2025-02-22 13:31 ` devin.buildroot [this message]
2025-02-22 13:31 ` [Buildroot] [PATCH 3/3] package/lttng-libust: bump to version 2.13.8 devin.buildroot
[not found] ` <20250222133127.9445-2-devin.buildroot__2127.52547101758$1740231125$gmane$org@gmail.com>
2025-11-15 16:50 ` [Buildroot] [PATCH 2/3] package/lttng-tools: bump to version 2.13.14 Bernd Kuhls
[not found] ` <20250222133127.9445-3-devin.buildroot__20167.7431746916$1740231130$gmane$org@gmail.com>
2025-11-15 16:51 ` [Buildroot] [PATCH 3/3] package/lttng-libust: bump to version 2.13.8 Bernd Kuhls
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=20250222133127.9445-2-devin.buildroot@gmail.com \
--to=devin.buildroot@gmail.com \
--cc=buildroot@buildroot.org \
--cc=eeppeliteloop@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox