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:44:47 +0100	[thread overview]
Message-ID: <87h935dznk.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <5f582368-797e-10ad-1c19-a998496cabbf@ya.ru> (Oleg Kitain's message of "Mon, 6 Mar 2017 03:02:02 +0300")

>>>>> "Oleg" == Oleg Kitain <okitain@ya.ru> writes:

 > 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.

Timing out several times? Is ftp access blocked in your firewall?

A missing file should not cause any timeout, it should simply generate
an error and fall back to sources.buildroot.net, E.G.:

wget ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/pcre-8.37.tar.bz2
--2017-03-07 13:43:28--  ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/pcre-8.37.tar.bz2
           => ?pcre-8.37.tar.bz2?
Resolving ftp.csx.cam.ac.uk (ftp.csx.cam.ac.uk)... 131.111.8.115
Connecting to ftp.csx.cam.ac.uk (ftp.csx.cam.ac.uk)|131.111.8.115|:21... connected.
Logging in as anonymous ... Logged in!
==> SYST ... done.    ==> PWD ... done.
==> TYPE I ... done.  ==> CWD (1) /pub/software/programming/pcre ... done.
==> SIZE pcre-8.37.tar.bz2 ... done.

==> PASV ... done.    ==> RETR pcre-8.37.tar.bz2 ...
No such file ?pcre-8.37.tar.bz2?.

-- 
Bye, Peter Korsgaard

      parent reply	other threads:[~2017-03-07 12:44 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
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 [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=87h935dznk.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.