From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] libseccomp: Version bump. 2.5.5 -> 2.6.0
Date: Fri, 21 Feb 2025 18:08:23 +0100 [thread overview]
Message-ID: <20250221170823.3903446-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20250125161419.1782179-1-christian.melki@t2data.com>
Thanks, applied as 31c508c4d8d4b0603c8ba6621e825ae222da36a3.
Michael
[sent from post-receive hook]
On Fri, 21 Feb 2025 18:08:23 +0100, Christian Melki <christian.melki@t2data.com> wrote:
> 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>
> Message-Id: <20250125161419.1782179-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> 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 48fbf8f7fc50..e424387d40eb 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)
prev parent reply other threads:[~2025-02-21 17:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-25 16:14 [ptxdist] [PATCH] " Christian Melki
2025-02-21 17:08 ` Michael Olbrich [this message]
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=20250221170823.3903446-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=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