[bitbake-devel] [PATCH] bitbake/fetch2: specify recipe name when reporting SRCREV error
Ross Burton
ross.burton at intel.com
Tue Jan 27 13:33:56 UTC 2015
The "SRCREV was used but no SCM found" error isn't that helpful when it doesn't
indicate *what* recipe does this, so add the filename to the message.
Signed-off-by: Ross Burton <ross.burton at intel.com>
---
bitbake/lib/bb/fetch2/__init__.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/bitbake/lib/bb/fetch2/__init__.py b/bitbake/lib/bb/fetch2/__init__.py
index 599ea8c..a24337c 100644
--- a/bitbake/lib/bb/fetch2/__init__.py
+++ b/bitbake/lib/bb/fetch2/__init__.py
@@ -637,7 +637,7 @@ def get_srcrev(d):
scms.append(u)
if len(scms) == 0:
- raise FetchError("SRCREV was used yet no valid SCM was found in SRC_URI")
+ raise FetchError("SRCREV was used yet no valid SCM was found in SRC_URI in %s" % d.getVar("FILE"))
if len(scms) == 1 and len(urldata[scms[0]].names) == 1:
autoinc, rev = urldata[scms[0]].method.sortable_revision(urldata[scms[0]], d, urldata[scms[0]].names[0])
--
1.7.10.4
More information about the bitbake-devel
mailing list