From: Christian Melki <christian.melki@t2data.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH v2] strace: Version bump. 5.15 -> 5.16
Date: Fri, 28 Jan 2022 11:34:26 +0100 [thread overview]
Message-ID: <20220128103426.1518111-1-christian.melki@t2data.com> (raw)
Mostly bugfixes.
Copyright year number range updated in COPYING file.
https://strace.io/files/5.16/
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 aa13f3e97..aeec39aa6 100644
--- a/rules/strace.make
+++ b/rules/strace.make
@@ -16,8 +16,8 @@ PACKAGES-$(PTXCONF_STRACE) += strace
#
# Paths and names
#
-STRACE_VERSION := 5.15
-STRACE_MD5 := a627c23fda3ecd668d6161c288fdcd79
+STRACE_VERSION := 5.16
+STRACE_MD5 := f848d24b2371948c91b57f72c0e75e66
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=318cfc887fc8723f4e9d4709b55e065b \
+ file://COPYING;md5=59a33f0a3e6122d67c0b3befccbdaa6b \
file://bundled/linux/COPYING;md5=391c7a5bbfb151ad3dbe0a7fb5791a46 \
file://bundled/linux/GPL-2.0;md5=e6a75371ba4d16749254a51215d13f97 \
file://LGPL-2.1-or-later;md5=9e4c7a7a5be83d7f3da645ac5d466052
--
2.30.2
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
next reply other threads:[~2022-01-28 10:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 10:34 Christian Melki [this message]
2022-02-04 17:44 ` Christian Melki
2022-02-04 18:14 ` Michael Olbrich
2022-02-04 18: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=20220128103426.1518111-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