From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Fetch failure for source at kernel.org
Date: Thu, 22 Sep 2011 01:26:48 +0100 [thread overview]
Message-ID: <1316651210.13622.0.camel@ted> (raw)
In-Reply-To: <30E0E33D-A811-4023-8977-4CA73C4656E6@dominion.thruhere.net>
On Wed, 2011-09-21 at 21:49 +0200, Koen Kooi wrote:
> Op 21 sep. 2011, om 21:43 heeft Mark Hatle het volgende geschreven:
>
> > 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.
>
> This is the "OE core doesn't generate versioned git tarballs" problem
> people keep talking about. I know I can edit each and every recipe to
> add ';rebasable=true', but I'd like a global solution before the GPL
> police starts looking at the angstrom source mirrors.
Is this a versioned tarball problem or just the tarballs not being
generated at all?
Are you setting BB_GENERATE_MIRROR_TARBALLS?
Cheers,
Richard
next prev parent reply other threads:[~2011-09-22 0:32 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
2011-09-21 19:49 ` Koen Kooi
2011-09-22 0:26 ` Richard Purdie [this message]
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=1316651210.13622.0.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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