From: Christian Melki <christian.melki@t2data.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH] strace: Version bump. 6.12 -> 6.13
Date: Sat, 25 Jan 2025 17:00:46 +0100 [thread overview]
Message-ID: <20250125160046.1762041-1-christian.melki@t2data.com> (raw)
Minor changes.
https://github.com/strace/strace/releases/tag/v6.13
* License hash changed. Copyright years updated.
Signed-off-by: Christian Melki <christian.melki@t2data.com>
---
rules/strace.make | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/rules/strace.make b/rules/strace.make
index 3848b6977..661417b49 100644
--- a/rules/strace.make
+++ b/rules/strace.make
@@ -16,8 +16,8 @@ PACKAGES-$(PTXCONF_STRACE) += strace
#
# Paths and names
#
-STRACE_VERSION := 6.12
-STRACE_MD5 := 6b774465c06b0dd01efc00a2db1341c2
+STRACE_VERSION := 6.13
+STRACE_MD5 := d6045bc205c1257a9f561670028cd63f
STRACE := strace-$(STRACE_VERSION)
STRACE_SUFFIX := tar.xz
STRACE_URL := https://strace.io/files/$(STRACE_VERSION)/$(STRACE).$(STRACE_SUFFIX)
@@ -25,7 +25,7 @@ STRACE_SOURCE := $(SRCDIR)/$(STRACE).$(STRACE_SUFFIX)
STRACE_DIR := $(BUILDDIR)/$(STRACE)
STRACE_LICENSE := LGPL-2.1-or-later AND GPL-2.0-only WITH Linux-syscall-note
STRACE_LICENSE_FILES := \
- file://COPYING;md5=2433d82e1432a76dc3eadd9002bfe304\
+ file://COPYING;md5=1efaf30bb0084b4a17a6f55f9cbcd25b \
file://bundled/linux/COPYING;md5=391c7a5bbfb151ad3dbe0a7fb5791a46 \
file://bundled/linux/GPL-2.0;md5=e6a75371ba4d16749254a51215d13f97 \
file://LGPL-2.1-or-later;md5=9e4c7a7a5be83d7f3da645ac5d466052
--
2.34.1
next reply other threads:[~2025-01-25 16:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-25 16:00 Christian Melki [this message]
2025-02-21 17:08 ` [ptxdist] [APPLIED] " Michael Olbrich
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=20250125160046.1762041-1-christian.melki@t2data.com \
--to=christian.melki@t2data.com \
--cc=ptxdist@pengutronix.de \
/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