Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Javier Viguera <javier.viguera@digi.com>
To: <openembedded-devel@lists.openembedded.org>,
	Tom King <ka6sox@gmail.com>,
	 Martin Jansa <martin.jansa@gmail.com>
Subject: Re: [meta-webserver] cherokee webserver SRC_URI broken again
Date: Mon, 19 May 2014 14:47:46 +0200	[thread overview]
Message-ID: <5379FD72.10407@digi.com> (raw)
In-Reply-To: <5370A2F8.50802@digi.com>

ping.

On 12/05/14 12:31, Javier Viguera wrote:
> Hi Martin,
>
> On 30/04/14 20:20, Martin Jansa wrote:
>> Tom, can you please put it on sources.oe.org?
>>
>> You can find the archive on aruba.
>
> Thanks for looking into this, but did this ever happen?
>
> I'm still having problems with cherokee download. In the fetch log it
> shows trying to get it from
> 'http://sources.openembedded.org/cherokee-1.2.98.tar.gz', but still no
> luck:
>
> $ wget http://sources.openembedded.org/cherokee-1.2.98.tar.gz
> --2014-05-12 12:29:11--
> http://sources.openembedded.org/cherokee-1.2.98.tar.gz
> Resolving sources.openembedded.org (sources.openembedded.org)...
> 140.211.169.152
> Connecting to sources.openembedded.org
> (sources.openembedded.org)|140.211.169.152|:80... connected.
> HTTP request sent, awaiting response... 404 Not Found
> 2014-05-12 12:29:11 ERROR 404: Not Found.
>
> -
> Javier Viguera
> Software Engineer
> Digi International® Spain S.A.U.


      reply	other threads:[~2014-05-19 12:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-30 16:13 [meta-webserver] cherokee webserver SRC_URI broken again Javier Viguera
2014-04-30 17:28 ` Paul Eggleton
2014-04-30 18:02   ` Javier Viguera
2014-04-30 18:20     ` Martin Jansa
2014-05-12 10:31       ` Javier Viguera
2014-05-19 12:47         ` Javier Viguera [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=5379FD72.10407@digi.com \
    --to=javier.viguera@digi.com \
    --cc=ka6sox@gmail.com \
    --cc=martin.jansa@gmail.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