All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] pcre: Change download location
Date: Tue, 07 Mar 2017 13:47:45 +0100	[thread overview]
Message-ID: <87d1dtdzim.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20170306212039.4134ccee@free-electrons.com> (Thomas Petazzoni's message of "Mon, 6 Mar 2017 21:20:39 +0100")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:

 > Hello,
 > On Mon, 6 Mar 2017 03:02:02 +0300, Oleg Kitain wrote:
 >> Subject: [PATCH 1/1] pcre: Change download location
 >> 
 >> The location at ftp.csx.cam.ac.uk only stores 2 latest versions of PCRE.
 >> This results in old (2015.11 and older currently) buildroot versions
 >> timing out on wget several times and having to retrieve the package
 >> from sources.buildroot.org afterwards.
 >> 
 >> Signed-off-by: Oleg Kitain <okitain@ya.ru>
 >> ---
 >> package/pcre/pcre.mk | 2 +-
 >> 1 file changed, 1 insertion(+), 1 deletion(-)

 > Applied to master, thanks. Peter: do we want this sort of fix in the
 > LTS release?

I'm a bit confused about the description. To me it sounds like a local
firewall issue with ftp access instead, but OK - Others might have a
similar setup.

Committed to 2017.02.x, thanks.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2017-03-07 12:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-06  0:02 [Buildroot] [PATCH 1/1] pcre: Change download location Oleg Kitain
2017-03-06 20:20 ` Thomas Petazzoni
2017-03-07 12:47   ` Peter Korsgaard [this message]
2017-03-07 13:02     ` Thomas Petazzoni
2017-03-07 14:03       ` Peter Korsgaard
2017-03-07 14:11         ` Thomas Petazzoni
2017-03-07 12:44 ` 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=87d1dtdzim.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@busybox.net \
    /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.