On Mon, 7 Jan 2013, Andrei Gherzan wrote:

I tested it today too and i ended up using a shared download
directory. The problem is at github. Will submit a bug (even if
somebody already did). More bugs - many changes to get it fixed
soon. Keep you posted.

i'm not currently at my dev machine so i can't test this, but i
noticed a while back that even when a bitbake git fetch failed, a
normal command-line "git clone" normally worked just fine.

so as a workaround, would it work to simply clone the github repo
somewhere on the dev host, then modify the recipe SRC_URI to use the
"file:" protocol, point it at the local clone, do the fetch/build, and
configure to create the resulting tarball, at which point you
shouldn't need to clone from github again (at least until the kernel
version was updated).

make sense? would this require simply changing the fetch protocol in
the kernel recipe's SRC_URI?

rday

--

========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================