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.1 -> 2.5.3.
Date: Fri, 21 Jan 2022 08:19:30 +0100 [thread overview]
Message-ID: <20220121071930.1968261-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20220107095253.36871-1-christian.melki@t2data.com>
Thanks, applied as 7ac1eb3eeb3870b4f4157abf809ac73978fa98ab.
Michael
[sent from post-receive hook]
On Fri, 21 Jan 2022 08:19:29 +0100, Christian Melki <christian.melki@t2data.com> wrote:
> Package maintenance.
> Move patch series to 2.5.3, applies cleanly.
>
> The patch is unlikely to cause harm, even though you can't assume bin/sh
> is POSIX capable (which seems to be the case).
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20220107095253.36871-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/patches/libseccomp-2.5.1/0001-run-time-use-a-broadly-supported-shell-interpreter.patch b/patches/libseccomp-2.5.3/0001-run-time-use-a-broadly-supported-shell-interpreter.patch
> similarity index 100%
> rename from patches/libseccomp-2.5.1/0001-run-time-use-a-broadly-supported-shell-interpreter.patch
> rename to patches/libseccomp-2.5.3/0001-run-time-use-a-broadly-supported-shell-interpreter.patch
> diff --git a/patches/libseccomp-2.5.1/series b/patches/libseccomp-2.5.3/series
> similarity index 100%
> rename from patches/libseccomp-2.5.1/series
> rename to patches/libseccomp-2.5.3/series
> diff --git a/rules/libseccomp.make b/rules/libseccomp.make
> index 9eb54245c756..5a6f45f1ccb2 100644
> --- a/rules/libseccomp.make
> +++ b/rules/libseccomp.make
> @@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_LIBSECCOMP) += libseccomp
> #
> # Paths and names
> #
> -LIBSECCOMP_VERSION := 2.5.1
> -LIBSECCOMP_MD5 := 59f5563c532d3fa1df9db0516b36b1cd
> +LIBSECCOMP_VERSION := 2.5.3
> +LIBSECCOMP_MD5 := 5096d3912a605a72b27805fa0ef9886d
> LIBSECCOMP := libseccomp-$(LIBSECCOMP_VERSION)
> LIBSECCOMP_SUFFIX := tar.gz
> LIBSECCOMP_URL := https://github.com/seccomp/libseccomp/releases/download/v$(LIBSECCOMP_VERSION)/$(LIBSECCOMP).$(LIBSECCOMP_SUFFIX)
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
prev parent reply other threads:[~2022-01-21 7:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 9:52 [ptxdist] [PATCH v2] " Christian Melki
2022-01-21 7:19 ` 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=20220121071930.1968261-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