From: Christian Melki <christian.melki@t2data.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH] libseccomp: Version bump. 2.5.5 -> 2.6.0
Date: Sat, 25 Jan 2025 17:14:19 +0100 [thread overview]
Message-ID: <20250125161419.1782179-1-christian.melki@t2data.com> (raw)
Two years since last update.
Added some new functionality.
There will probably be a continuation on the 2.5.x series,
but I decided to step to 2.6.0 instead.
https://github.com/seccomp/libseccomp/releases/tag/v2.6.0
* Patchset forwarded. Applies cleanly.
Signed-off-by: Christian Melki <christian.melki@t2data.com>
---
...1-run-time-use-a-broadly-supported-shell-interpreter.patch | 0
patches/{libseccomp-2.5.5 => libseccomp-2.6.0}/series | 0
rules/libseccomp.make | 4 ++--
3 files changed, 2 insertions(+), 2 deletions(-)
rename patches/{libseccomp-2.5.5 => libseccomp-2.6.0}/0001-run-time-use-a-broadly-supported-shell-interpreter.patch (100%)
rename patches/{libseccomp-2.5.5 => libseccomp-2.6.0}/series (100%)
diff --git a/patches/libseccomp-2.5.5/0001-run-time-use-a-broadly-supported-shell-interpreter.patch b/patches/libseccomp-2.6.0/0001-run-time-use-a-broadly-supported-shell-interpreter.patch
similarity index 100%
rename from patches/libseccomp-2.5.5/0001-run-time-use-a-broadly-supported-shell-interpreter.patch
rename to patches/libseccomp-2.6.0/0001-run-time-use-a-broadly-supported-shell-interpreter.patch
diff --git a/patches/libseccomp-2.5.5/series b/patches/libseccomp-2.6.0/series
similarity index 100%
rename from patches/libseccomp-2.5.5/series
rename to patches/libseccomp-2.6.0/series
diff --git a/rules/libseccomp.make b/rules/libseccomp.make
index 48fbf8f7f..e424387d4 100644
--- a/rules/libseccomp.make
+++ b/rules/libseccomp.make
@@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_LIBSECCOMP) += libseccomp
#
# Paths and names
#
-LIBSECCOMP_VERSION := 2.5.5
-LIBSECCOMP_MD5 := c27a5e43cae1e89e6ebfedeea734c9b4
+LIBSECCOMP_VERSION := 2.6.0
+LIBSECCOMP_MD5 := 2d42bcde31fd6e994fcf251a1f71d487
LIBSECCOMP := libseccomp-$(LIBSECCOMP_VERSION)
LIBSECCOMP_SUFFIX := tar.gz
LIBSECCOMP_URL := https://github.com/seccomp/libseccomp/releases/download/v$(LIBSECCOMP_VERSION)/$(LIBSECCOMP).$(LIBSECCOMP_SUFFIX)
--
2.34.1
next reply other threads:[~2025-01-25 16:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-25 16:14 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=20250125161419.1782179-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