<div dir="ltr"><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Dec 31, 2012 at 10:15 AM, Robert P. J. Day <span dir="ltr"><<a href="mailto:rpjday@crashcourse.ca" target="_blank">rpjday@crashcourse.ca</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":1nk"> i'm sure it's something i'm doing but i'm playing with an OE<br>
configuration for qemuarm and experimenting with "bitbake -e" and got<br>
this:<br>
<br>
$ bitbake -e core-image-minimal | grep SRCREV<br>
... snip ...<br>
# expansion of SRCPV threw ExpansionError: Failure expanding variable<br>
SRCPV, expression was ${@bb.fetch2.get_srcrev(d)} which triggered<br>
exception FetchError: Fetcher failure: SRCREV was used yet no valid<br>
SCM was found in SRC_URI<br>
# SRCREV=INVALID<br>
SRCREV="INVALID"<br>
... snip ...<br>
$<br>
<br>
i can appreciate *why* this is happening if the fetcher code thinks<br>
that's a valid value for SRCREV but there's no SRC_URI value for<br>
core-image-minimal.<br>
<br>
i've googled a bit and perused the code but i'm guessing someone<br>
else can probably see what's happening in seconds. the above doesn't<br>
appear to hurt anything, but it certainly seems like a bogus error.</div></blockquote></div><br>This error is raised whenever SRCPV is expanded. When not using -e, that only occurs if you set PV to include SRCPV. When using -e, it forces expansion of every variable, including that one. It's essentially harmless, as -e is only useful for inspection. Were we to silence all expansion failures when using -e, it would be easy to miss an actual harmful failure when trying to inspect a particular variable you require, which is why we don't do that. In this case, however, you can safely ignore it.<br>
-- <br>Christopher Larson</div></div>