From: Khem Raj <raj.khem@gmail.com>
To: Saul Wold <sgw@linux.intel.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [RFC] DISTRO_MIRRORS / DISTRO_PREMIRRORS
Date: Wed, 15 Jun 2011 09:30:11 -0700 [thread overview]
Message-ID: <4DF8DE13.9000105@gmail.com> (raw)
In-Reply-To: <4DF8DD33.1020006@linux.intel.com>
On 06/15/2011 09:26 AM, Saul Wold wrote:
> On 06/15/2011 09:13 AM, Khem Raj wrote:
>> On 06/15/2011 09: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.
>>>
>>> diff --git a/meta/classes/mirrors.bbclass b/meta/classes/mirrors.bbclass
>>> index 2146087..a52c6d5 100644
>>> --- a/meta/classes/mirrors.bbclass
>>> +++ b/meta/classes/mirrors.bbclass
>>> @@ -1,4 +1,22 @@
>>> +DISTRO_PREMIRRORS ?= "\
>>> +bzr://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \
>>> +cvs://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \
>>> +git://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \
>>> +hg://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \
>>> +osc://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \
>>> +p4://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \
>>> +svk://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \
>>> +svn://.*/.* http://autobuilder.yoctoproject.org/sources/ \n"
>>> +
>>> +PREMIRRORS += "${DISTRO_PREMIRRORS}"
>>> +
>>> +DISTRO_MIRRORS ?= "\
>>> +ftp://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \
>>> +http://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \
>>> +https://.*/.* http://autobuilder.yoctoproject.org/sources/ \n"
>>> +
>>> MIRRORS += "\
>>> +${DISTRO_MIRRORS} \
>>> ${DEBIAN_MIRROR}/main http://snapshot.debian.net/archive/pool \n \
>>> ${DEBIAN_MIRROR} ftp://ftp.de.debian.org/debian/pool \n \
>>> ${DEBIAN_MIRROR} ftp://ftp.au.debian.org/debian/pool \n \
>>>
>>> Thoughts, ACKs, NAKs??
>>>
>>
>> FWIW http://mirrors.openembedded.org/ also exists.
>>>
> How up to date is it and how is it maintained? Is it possible for this
> mirror site to fall behind oe-core?
>
oe.dev falls back to it by default and whenever there is a report of non
existing tars they are put up there.
> Sau!
>
>>> --
>>> 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
>>
>>
>> _______________________________________________
>> 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:33 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
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 [this message]
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=4DF8DE13.9000105@gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=sgw@linux.intel.com \
/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