From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: should SRC_URI for mpfr be switched to ftp.gnu.org?
Date: Wed, 09 Jan 2013 13:32:08 +0000 [thread overview]
Message-ID: <1357738328.13022.76.camel@ted> (raw)
In-Reply-To: <alpine.DEB.2.02.1301090656070.14444@oneiric>
On Wed, 2013-01-09 at 06:58 -0500, Robert P. J. Day wrote:
> currently, fetching from mpfr's official SRC_URI,
> http://www.mpfr.org/mpfr-${PV}/mpfr-${PV}.tar.bz2, is failing, and i
> can't even browse there. however, mpfr seems well supported here:
>
> http://ftp.gnu.org/gnu/mpfr/
>
> is there any incentive to switch SRC_URI, or is mpfr.org the official
> download site and this is just a temporary glitch of some kind?
It should probably get listed as a mirror assuming the mpfr site will
come back...
Cheers,
Richard
prev parent reply other threads:[~2013-01-09 13:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-09 11:58 should SRC_URI for mpfr be switched to ftp.gnu.org? Robert P. J. Day
2013-01-09 13:32 ` Richard Purdie [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=1357738328.13022.76.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=rpjday@crashcourse.ca \
/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