From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Bruno Thomsen <bruno.thomsen@gmail.com>
Subject: Re: [ptxdist] [APPLIED] gnupg: add extra https source url
Date: Wed, 25 May 2022 11:44:57 +0200 [thread overview]
Message-ID: <20220525094457.2844223-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20220510081916.3297-1-bruno.thomsen@gmail.com>
Thanks, applied as 9a2b81d60e8ab739de2e923d3f4f4f736aa5cb2d.
Michael
[sent from post-receive hook]
On Wed, 25 May 2022 11:44:56 +0200, Bruno Thomsen <bruno.thomsen@gmail.com> wrote:
> ftp.gnupg.org seems to be unstable and/or unreachable from a lot of
> networks.
>
> Signed-off-by: Bruno Thomsen <bruno.thomsen@gmail.com>
> Message-Id: <20220510081916.3297-1-bruno.thomsen@gmail.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/gnupg.make b/rules/gnupg.make
> index cdf70e9edffb..25d267769443 100644
> --- a/rules/gnupg.make
> +++ b/rules/gnupg.make
> @@ -19,7 +19,9 @@ GNUPG_VERSION := 2.2.23
> GNUPG_MD5 := a094ff856a53a9a9fd5465657d998079
> GNUPG := gnupg-$(GNUPG_VERSION)
> GNUPG_SUFFIX := tar.bz2
> -GNUPG_URL := ftp://ftp.gnupg.org/gcrypt/gnupg/$(GNUPG).$(GNUPG_SUFFIX)
> +GNUPG_URL := \
> + https://www.gnupg.org/ftp/gcrypt/gnupg/$(GNUPG).$(GNUPG_SUFFIX) \
> + ftp://ftp.gnupg.org/gcrypt/gnupg/$(GNUPG).$(GNUPG_SUFFIX)
> GNUPG_SOURCE := $(SRCDIR)/$(GNUPG).$(GNUPG_SUFFIX)
> GNUPG_DIR := $(BUILDDIR)/$(GNUPG)
> GNUPG_LICENSE := GPL-3.0-or-later
prev parent reply other threads:[~2022-05-25 9:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 8:19 [ptxdist] [PATCH 1/3] " Bruno Thomsen
2022-05-10 8:19 ` [ptxdist] [PATCH 2/3] libksba: " Bruno Thomsen
2022-05-25 9:44 ` [ptxdist] [APPLIED] " Michael Olbrich
2022-05-10 8:19 ` [ptxdist] [PATCH 3/3] npth: " Bruno Thomsen
2022-05-25 9:44 ` [ptxdist] [APPLIED] " Michael Olbrich
2022-05-25 9:44 ` 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=20220525094457.2844223-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=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