From: Javier Viguera <javier.viguera@digi.com>
To: "Eric Bénard" <eric@eukrea.com>
Cc: "openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>
Subject: cherokee wrong SRC_URI (was Dylan backports)
Date: Thu, 7 Nov 2013 17:02:25 +0100 [thread overview]
Message-ID: <527BB991.8060008@digi.com> (raw)
In-Reply-To: <20131107161445.589ad9ea@e6520eb>
Hi Eric,
On 07/11/13 16:14, Eric Bénard wrote:
> that's now pushed, thanks for the reminder.
>
> Eric
Well I should have probably checked that the mirror was still working
before sending my e-mail but you know ... Murphy's law.
The thing is that for cherokee the mirror I used to download the package
from has removed it since i sent the patch a couple of months ago.
I'm sorry to have pushed you to merge the patches. Anyway from
meta-openembedded point of view the status has *not* gone any worse. It
was not working before (with old cherokee url) and it's not working now
as well.
I've found a couple of sites with the original package (same md5sum and
sha256sum):
<ftp://ftp.nluug.nl/pub/internet/cherokee/1.2/1.2.98/cherokee-1.2.98.tar.gz>
<ftp://ftp.heanet.ie/mirrors/cherokee/1.2/1.2.98/cherokee-1.2.98.tar.gz>
but at this moment I'm not sure whether it's worth to keep changing the
SRC_URI time and time again.
Probably the way to go is to revert my patch leaving the original
cherokee as a reference and include the package in any of the
yoctoproject mirrors.
By the way the recipe is now broken not only in Dylan, but also in
*Dora* and *master*.
Comments?
-
Javier Viguera
Software Engineer
Digi International® Spain S.A.U.
next prev parent reply other threads:[~2013-11-07 16:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-10 15:55 Dylan backports Javier Viguera
2013-10-10 19:31 ` Eric Bénard
2013-11-07 14:50 ` Javier Viguera
2013-11-07 15:14 ` Eric Bénard
2013-11-07 16:02 ` Javier Viguera [this message]
2013-11-07 16:45 ` cherokee wrong SRC_URI (was Dylan backports) Paul Eggleton
2013-11-07 17:12 ` Javier Viguera
2013-11-07 18:25 ` Paul Eggleton
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=527BB991.8060008@digi.com \
--to=javier.viguera@digi.com \
--cc=eric@eukrea.com \
--cc=openembedded-devel@lists.openembedded.org \
/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