From: Robert Schwebel <r.schwebel@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Robert Schwebel <r.schwebel@pengutronix.de>
Subject: [ptxdist] [PATCH 4/6] libseccomp: version bump 2.3.1 -> 2.3.2
Date: Tue, 25 Apr 2017 00:18:59 +0200 [thread overview]
Message-ID: <20170424221901.7445-4-r.schwebel@pengutronix.de> (raw)
In-Reply-To: <20170424221901.7445-1-r.schwebel@pengutronix.de>
There are no relevant configure.ac changes.
There are no patches.
Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
---
rules/libseccomp.make | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/rules/libseccomp.make b/rules/libseccomp.make
index 1b68b31c4..4196736d1 100644
--- a/rules/libseccomp.make
+++ b/rules/libseccomp.make
@@ -16,8 +16,8 @@ PACKAGES-$(PTXCONF_LIBSECCOMP) += libseccomp
#
# Paths and names
#
-LIBSECCOMP_VERSION := 2.3.1
-LIBSECCOMP_MD5 := e6f3e84921ef9c2e9188681963f0943f
+LIBSECCOMP_VERSION := 2.3.2
+LIBSECCOMP_MD5 := e74a626bea0cd607c23229b10b5f93da
LIBSECCOMP := libseccomp-$(LIBSECCOMP_VERSION)
LIBSECCOMP_SUFFIX := tar.gz
LIBSECCOMP_URL := https://github.com/seccomp/libseccomp/releases/download/v$(LIBSECCOMP_VERSION)/$(LIBSECCOMP).$(LIBSECCOMP_SUFFIX)
--
2.11.0
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2017-04-24 22:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-24 22:18 [ptxdist] [PATCH 1/6] gnutls: version bump 3.3.25 -> 3.3.27 Robert Schwebel
2017-04-24 22:18 ` [ptxdist] [PATCH 2/6] expat: version bump 2.1.1 -> 2.2.0 Robert Schwebel
2017-04-24 22:18 ` [ptxdist] [PATCH 3/6] gmp: version bump 6.0.0a -> 6.1.2 Robert Schwebel
2017-04-24 22:18 ` Robert Schwebel [this message]
2017-04-24 22:19 ` [ptxdist] [PATCH 5/6] libnewt: version bump 0.52.18 -> 0.52.20 Robert Schwebel
2017-04-28 13:21 ` Michael Olbrich
2017-04-30 9:26 ` [ptxdist] [PATCHv2] " Robert Schwebel
2017-04-24 22:19 ` [ptxdist] [PATCH 6/6] popt: version bump 1.15 -> 1.16 Robert Schwebel
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=20170424221901.7445-4-r.schwebel@pengutronix.de \
--to=r.schwebel@pengutronix.de \
--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