From: Bruno Thomsen <bruno.thomsen@gmail.com>
To: ptxdist@pengutronix.de
Cc: Bruno Thomsen <bruno.thomsen@gmail.com>
Subject: [ptxdist] [PATCH 1/6] npth: version bump 1.5 -> 1.6
Date: Fri, 29 Jul 2022 11:26:49 +0200 [thread overview]
Message-ID: <20220729092654.3861-1-bruno.thomsen@gmail.com> (raw)
Ensure GnuPG has up-to-date dependencies.
Signed-off-by: Bruno Thomsen <bruno.thomsen@gmail.com>
---
rules/npth.make | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/rules/npth.make b/rules/npth.make
index 665668fd524f..baa9ab3aabab 100644
--- a/rules/npth.make
+++ b/rules/npth.make
@@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_NPTH) += npth
#
# Paths and names
#
-NPTH_VERSION := 1.5
-NPTH_MD5 := 9ba2dc4302d2f32c66737c43ed191b1b
+NPTH_VERSION := 1.6
+NPTH_MD5 := 375d1a15ad969f32d25f1a7630929854
NPTH := npth-$(NPTH_VERSION)
NPTH_SUFFIX := tar.bz2
NPTH_URL := \
base-commit: 02f8e5e7cb2ae088b69bfd2d75ba9e702eeaac5f
--
2.37.1
next reply other threads:[~2022-07-29 9:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 9:26 Bruno Thomsen [this message]
2022-07-29 9:26 ` [ptxdist] [PATCH 2/6] libgpg-error: version bump 1.42 -> 1.45 Bruno Thomsen
2022-08-04 15:14 ` [ptxdist] [APPLIED] " Michael Olbrich
2022-07-29 9:26 ` [ptxdist] [PATCH 3/6] libgcrypt: version bump 1.8.8 -> 1.10.1 Bruno Thomsen
2022-08-04 15:14 ` [ptxdist] [APPLIED] " Michael Olbrich
2022-07-29 9:26 ` [ptxdist] [PATCH 4/6] libksba: version bump 1.3.5 -> 1.6.0 Bruno Thomsen
2022-08-04 15:14 ` [ptxdist] [APPLIED] " Michael Olbrich
2022-07-29 9:26 ` [ptxdist] [PATCH 5/6] gnupg: version bump 2.2.23 -> 2.3.7 Bruno Thomsen
2022-08-05 7:50 ` [ptxdist] [APPLIED] " Michael Olbrich
2022-07-29 9:26 ` [ptxdist] [PATCH 6/6] gnupg: add license files and update spdx identifiers Bruno Thomsen
2022-07-29 10:38 ` Michael Olbrich
2022-08-04 15:14 ` [ptxdist] [APPLIED] npth: version bump 1.5 -> 1.6 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=20220729092654.3861-1-bruno.thomsen@gmail.com \
--to=bruno.thomsen@gmail.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