From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Bruno Thomsen <bruno.thomsen@gmail.com>
Subject: Re: [ptxdist] [APPLIED] libksba: add extra https source url
Date: Wed, 25 May 2022 11:44:58 +0200 [thread overview]
Message-ID: <20220525094458.2844300-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20220510081916.3297-2-bruno.thomsen@gmail.com>
Thanks, applied as f7e68cb4a631b490d9bfb21f8560ec9c4a2f1ddc.
Michael
[sent from post-receive hook]
On Wed, 25 May 2022 11:44:58 +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-2-bruno.thomsen@gmail.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/libksba.make b/rules/libksba.make
> index 554440cbede7..0604beb1fa53 100644
> --- a/rules/libksba.make
> +++ b/rules/libksba.make
> @@ -18,7 +18,9 @@ LIBKSBA_VERSION := 1.3.5
> LIBKSBA_MD5 := 8302a3e263a7c630aa7dea7d341f07a2
> LIBKSBA := libksba-$(LIBKSBA_VERSION)
> LIBKSBA_SUFFIX := tar.bz2
> -LIBKSBA_URL := ftp://ftp.gnupg.org/gcrypt/libksba/$(LIBKSBA).$(LIBKSBA_SUFFIX)
> +LIBKSBA_URL := \
> + https://www.gnupg.org/ftp/gcrypt/libksba/$(LIBKSBA).$(LIBKSBA_SUFFIX) \
> + ftp://ftp.gnupg.org/gcrypt/libksba/$(LIBKSBA).$(LIBKSBA_SUFFIX)
> LIBKSBA_SOURCE := $(SRCDIR)/$(LIBKSBA).$(LIBKSBA_SUFFIX)
> LIBKSBA_DIR := $(BUILDDIR)/$(LIBKSBA)
> LIBKSBA_LICENSE := GPL-2.0-only AND GPL-3.0-only AND LGPL-3.0-only
next 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] gnupg: " Bruno Thomsen
2022-05-10 8:19 ` [ptxdist] [PATCH 2/3] libksba: " Bruno Thomsen
2022-05-25 9:44 ` Michael Olbrich [this message]
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 ` [ptxdist] [APPLIED] gnupg: " 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=20220525094458.2844300-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