From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Dario Binacchi <dariobin@libero.it>
Cc: Dario Binacchi <dario.binacchi@amarulasolutions.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/pcre2: fix broken URL
Date: Thu, 9 Dec 2021 19:17:31 +0100 [thread overview]
Message-ID: <20211209181731.GG2603@scaer> (raw)
In-Reply-To: <20211209082148.22068-1-dariobin@libero.it>
Dario, All,
On 2021-12-09 09:21 +0100, Dario Binacchi via buildroot spake thusly:
> As stated on www.pcre.org:
> "Note that the former ftp.pcre.org FTP site is no longer available."
>
> Update _SITE URL to Sourceforge.
Note that the same www.pcre.org states (emphasize mine):
You can download the current release of the PCRE2 library from its
**official** home on GitHub: [...]
So I've applied, but switched to Github instead of SF.
Regards,
Yann E. MORIN.
> Signed-off-by: Dario Binacchi <dariobin@libero.it>
> Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>
> ---
> package/pcre2/pcre2.hash | 2 +-
> package/pcre2/pcre2.mk | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/package/pcre2/pcre2.hash b/package/pcre2/pcre2.hash
> index 130ce1f596..e0d5f37229 100644
> --- a/package/pcre2/pcre2.hash
> +++ b/package/pcre2/pcre2.hash
> @@ -1,5 +1,5 @@
> # Locally calculated after checking pgp signature
> -# https://ftp.pcre.org/pub/pcre/pcre2-10.37.tar.bz2.sig
> +# http://downloads.sourceforge.net/project/pcre/pcre2/10.37/pcre2-10.37.tar.bz2.sig
> sha256 4d95a96e8b80529893b4562be12648d798b957b1ba1aae39606bbc2ab956d270 pcre2-10.37.tar.bz2
> # Locally computed
> sha256 9c9488256e3612ec5ea40fd12abe7ec55a58f23bd36e6f465116c2b3cbffba02 LICENCE
> diff --git a/package/pcre2/pcre2.mk b/package/pcre2/pcre2.mk
> index 220eb8a99c..b24afb7ca4 100644
> --- a/package/pcre2/pcre2.mk
> +++ b/package/pcre2/pcre2.mk
> @@ -5,7 +5,7 @@
> ################################################################################
>
> PCRE2_VERSION = 10.37
> -PCRE2_SITE = https://ftp.pcre.org/pub/pcre
> +PCRE2_SITE = http://downloads.sourceforge.net/project/pcre/pcre2/$(PCRE_VERSION)
> PCRE2_SOURCE = pcre2-$(PCRE2_VERSION).tar.bz2
> PCRE2_LICENSE = BSD-3-Clause
> PCRE2_LICENSE_FILES = LICENCE
> --
> 2.17.1
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-12-09 18:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 8:21 [Buildroot] [PATCH 1/1] package/pcre2: fix broken URL Dario Binacchi via buildroot
2021-12-09 18:17 ` Yann E. MORIN [this message]
2022-01-14 15:54 ` Peter Korsgaard
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=20211209181731.GG2603@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=dario.binacchi@amarulasolutions.com \
--cc=dariobin@libero.it \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.