From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Frans Meulenbroeks <fransmeulenbroeks@gmail.com>,
openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: non-fetching recipes
Date: Wed, 28 Dec 2011 11:43:07 -0800 [thread overview]
Message-ID: <4EFB714B.30206@linux.intel.com> (raw)
In-Reply-To: <CACW_hTbBoB4yaN0W+H3WuW9GXYFGD6+FxQ5BMbKe+a2-pqc_Hw@mail.gmail.com>
On 12/28/2011 02:33 AM, Frans Meulenbroeks wrote:
> Hi,
>
> I noticed that several recipes are non-fetchers. These are mostly the
> ones with sources hosted on kernel.org <http://kernel.org>.
> Is there an issue with kernel.org <http://kernel.org> again?
>
It's not down again, a number of the sources have not been restored or
have been moved, still trying to track some of this down.
There should be source mirrors at the yoctoproject.org website as well
as the openembedded,org site (not sure if this full url).
> I noticed this for oe classic where libpam and util-linux-ng did not
> fetch (as well as opkg-utils but that one is from openmoko).
> oe maintenance branch seems to have the same problems as well as using
> binutils 2.21 which is not available any more. master does not have this
> as it has been moved to 2.21a.
>
> I'm crossposting this to oe-core, because I noticed it uses the same
> location for libpam (and probably util-linux).
>
> Someone might want to run some fetchalls.
>
We do run a nightly fetch, but I think we have our mirror set so we
don't see the full fails, it might be a good idea to figure out the
complete failure set right now with no PREMIRROR or MIRRRORs.
I will look into this.
Sau!
> Frans.
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
prev parent reply other threads:[~2011-12-28 19:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-28 10:33 non-fetching recipes Frans Meulenbroeks
2011-12-28 19:43 ` Saul Wold [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=4EFB714B.30206@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=fransmeulenbroeks@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--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