From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [RFC] DISTRO_MIRRORS / DISTRO_PREMIRRORS
Date: Wed, 15 Jun 2011 11:11:18 -0500 [thread overview]
Message-ID: <4DF8D9A6.3020606@windriver.com> (raw)
In-Reply-To: <4DF8D848.9000605@linux.intel.com>
On 6/15/11 11:05 AM, Saul Wold wrote:
>
> Folks,
>
> Recently we have seen a number of fetch failures, due to upstream sites
> being down or deprecated (tinylogin, pscmic and others).
>
> The issue is that oe-core as a non-distro does not have a default set of
> mirrors, which causes the fetcher to fail as there is no fall-back
> mirror to distrubte the source code.
>
> As has been pointed out, different projects and distributions (Yocto
> Project and Angstrom) both have upstream source mirrors which could be
> used. Currently the Yocto Project defines it's MIRRORS and PREMIRRORS in
> meta-yocto/conf/distro/poky.conf.
>
> I propose that we add a list of DISTO_MIRRORS and DISTRO_PREMIRRORS with
> default settings pointing to the current autobuilder.yoctoproject.org
> source site. These would be added to the mirrors.bbclass, so that
> oe-core will have a default set of mirrors that can be overridden by a
> distro or layer.
>
...
>
> Thoughts, ACKs, NAKs??
The only concern I have is that we may miss when an upstream source location
changes, thus not fixing a recipe when a package moves, disappears and otherwise
can't be downloaded.
--Mark
> --
> Sau!
>
> Saul Wold
> Yocto Component Wrangler @ Intel
> Yocto Project / Poky Build System
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2011-06-15 16:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-15 16:05 [RFC] DISTRO_MIRRORS / DISTRO_PREMIRRORS Saul Wold
2011-06-15 16:11 ` Mark Hatle [this message]
2011-06-15 16:22 ` Khem Raj
2011-06-15 16:13 ` Khem Raj
2011-06-15 16:26 ` Saul Wold
2011-06-15 16:30 ` Khem Raj
2011-06-16 0:31 ` Tom Rini
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=4DF8D9A6.3020606@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@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