From: "Sébastien Szymanski" <sebastien.szymanski@armadeus.com>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/pcre: fix broken URL
Date: Fri, 19 Nov 2021 11:36:32 +0100 [thread overview]
Message-ID: <47a68b89-d935-59f3-b051-c60c3e2d33d1@armadeus.com> (raw)
In-Reply-To: <20211119101140.GN247986@scaer>
Hi Yann,
On 11/19/21 11:11, Yann E. MORIN wrote:
> Sébastien, All,
>
> On 2021-11-19 09:59 +0100, Sébastien Szymanski 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.
>
> The homepage states that the official release channel is github, and
> that sourceforge is unoficial:
>
> http://www.pcre.org/
>
> You can download the current release of the PCRE2 library from its
> official home on GitHub:
>
> https://github.com/PhilipHazel/pcre2/releases
>
> You can also download PCRE2 or the older, unmaintained PCRE library
> from an unofficial mirror at SourceForge:
>
> https://sourceforge.net/projects/pcre/files/
>
> So could you respin using the release from github, pleasE?
No, I can't because there are pcre2 (two) releases only on github...
As explained in what you copied / pasted, older releases are on SourceForge.
Regards,
>
> Regards,
> Yann E. MORIN.
>
>> Signed-off-by: Sébastien Szymanski <sebastien.szymanski@armadeus.com>
>> ---
>> package/pcre/pcre.mk | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/package/pcre/pcre.mk b/package/pcre/pcre.mk
>> index 264eaa10c7..c85f6717db 100644
>> --- a/package/pcre/pcre.mk
>> +++ b/package/pcre/pcre.mk
>> @@ -5,7 +5,7 @@
>> ################################################################################
>>
>> PCRE_VERSION = 8.45
>> -PCRE_SITE = https://ftp.pcre.org/pub/pcre
>> +PCRE_SITE = http://downloads.sourceforge.net/project/pcre/pcre/$(PCRE_VERSION)
>> PCRE_SOURCE = pcre-$(PCRE_VERSION).tar.bz2
>> PCRE_LICENSE = BSD-3-Clause
>> PCRE_LICENSE_FILES = LICENCE
>> --
>> 2.32.0
>>
>> _______________________________________________
>> buildroot mailing list
>> buildroot@buildroot.org
>> https://lists.buildroot.org/mailman/listinfo/buildroot
>
--
Sébastien Szymanski, Armadeus Systems
Software engineer
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-11-19 10:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-19 8:59 [Buildroot] [PATCH 1/1] package/pcre: fix broken URL Sébastien Szymanski
2021-11-19 10:11 ` Yann E. MORIN
2021-11-19 10:36 ` Sébastien Szymanski [this message]
2021-11-19 16:05 ` Yann E. MORIN
2021-12-06 22:11 ` 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=47a68b89-d935-59f3-b051-c60c3e2d33d1@armadeus.com \
--to=sebastien.szymanski@armadeus.com \
--cc=buildroot@buildroot.org \
--cc=yann.morin.1998@free.fr \
/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.