Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: Fetch failure for source at kernel.org
Date: Wed, 21 Sep 2011 14:43:08 -0500	[thread overview]
Message-ID: <4E7A3E4C.6080206@windriver.com> (raw)
In-Reply-To: <4E7A3D3A.1030007@balister.org>

On 9/21/11 2:38 PM, Philip Balister wrote:
> I'm finally trying to get started with oe-core. I'm using a setup 
> created with the setup-script created by Koen. Everything looks ok until 
> it tried to build cpufrequtils. The recipe tries to fetch the source 
> from a git repo at kernel.org. Obviously, the fetch fails.
> 
> What is odd, in the "good old days" I would expect this config to fall 
> back and use the Angstrom source mirror, but apparently this is not the 
> case with oe-core.
> 
> Is this a bug or a feature? If this is a bug, is there a plan to fix it? 
> If it is a feature, how are we supposed to do builds if servers go away? 
> What do we do about GPL compliance?

This is a feature, as people did not want oe-core tied to a given mirror.

Myself, I use:

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"

MIRRORS =+ "\
ftp://.*/.*    http://autobuilder.yoctoproject.org/sources/ \n \
http://.*/.*     http://autobuilder.yoctoproject.org/sources/ \n \
https://.*/.*    http://autobuilder.yoctoproject.org/sources/ \n"

PREMIRRORS are tried before the upstream source, MIRRORS are tried only after a
failure.  (Please correct me someone if I have that wrong.)

--Mark

> Thanks,
> 
> Philip
> 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core




  reply	other threads:[~2011-09-21 19:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-21 19:38 Fetch failure for source at kernel.org Philip Balister
2011-09-21 19:43 ` Mark Hatle [this message]
2011-09-21 19:49   ` Koen Kooi
2011-09-22  0:26     ` Richard Purdie
2011-09-22  6:40       ` Koen Kooi
2011-09-22  7:03         ` Richard Purdie
2011-09-22  8:28           ` Koen Kooi
2011-09-22  8:45             ` Martin Jansa
2011-09-22  9:01               ` Koen Kooi
2011-09-22 10:20             ` Richard Purdie
2011-09-22 11:27               ` Koen Kooi
2011-09-22 11:42                 ` Richard Purdie
2011-09-22 12:13                   ` Koen Kooi

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=4E7A3E4C.6080206@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