Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: some more non fetching recipes
Date: Sun, 26 Sep 2010 13:27:00 +0200	[thread overview]
Message-ID: <20100926112659.GB6483@jama> (raw)
In-Reply-To: <AANLkTi=Wt1eRcSoXzjwMJizLBgQ-+hV=Xj1UWW155MWQ@mail.gmail.com>

On Sun, Sep 26, 2010 at 12:21:36PM +0200, Frans Meulenbroeks wrote:
> Apart from the opensync and uclibc recipes that did not fetch and were
> reported before, I did get fetch issues for the files below.
> Haven't had time to dig into these, so some of these might be false alarms.
> If anyone feels attached to a recipe or can say something about it,
> please take action.

There was about ~1000 recipes failing to fetch few months ago, I don't
think this number is that much lower as I haven't seen any changes in
most of them.

See my download status:
http://lists.linuxtogo.org/pipermail/openembedded-devel/2010-April/019206.html
http://lists.linuxtogo.org/pipermail/openembedded-devel/2010-April/019234.html

but I was testing not only latest version, but all versions and for all
ARCHs.

Regards,

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com



  parent reply	other threads:[~2010-09-26 11:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-26 10:21 some more non fetching recipes Frans Meulenbroeks
2010-09-26 11:13 ` Holger Freyther
2010-09-26 11:58   ` Frans Meulenbroeks
2010-09-26 11:27 ` Martin Jansa [this message]
2010-09-26 12:14   ` Frans Meulenbroeks
2010-09-27  6:19   ` Frans Meulenbroeks
2010-09-27 11:49     ` Mike Westerhof
2010-09-27 12:51       ` Frans Meulenbroeks
2010-09-27 13:04         ` Martin Jansa
2010-10-03 11:46 ` Martin Jansa
2010-10-03 12:15   ` Frans Meulenbroeks

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=20100926112659.GB6483@jama \
    --to=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