aboutsummaryrefslogtreecommitdiffstats
path: root/meta/recipes-extended
diff options
context:
space:
mode:
authorPaul Eggleton <paul.eggleton@linux.intel.com>2016-01-23 01:00:01 +1300
committerRichard Purdie <richard.purdie@linuxfoundation.org>2016-01-22 23:42:57 +0000
commit578d3873a6415c9203c185c21cff472f7d2dab02 (patch)
tree75c2ad9dc3c6c0327b61662f78accc304cf64f59 /meta/recipes-extended
parent308189beda8a31541481d09e3d5e86187e843d8d (diff)
downloadopenembedded-core-contrib-578d3873a6415c9203c185c21cff472f7d2dab02.tar.gz
openembedded-core-contrib-578d3873a6415c9203c185c21cff472f7d2dab02.tar.bz2
openembedded-core-contrib-578d3873a6415c9203c185c21cff472f7d2dab02.zip
recipetool: create: better fix for fetch error handling
I was a little bit hasty in OE-Core revision c2cc5abe34169eae92067d97ce1e747e7c1413f5 - it turns out BitBake's fetcher code is not consistent in whether it logs something useful or not; when fetching from an http URL it does but with a git repository it doesn't. In advance of any major reworking of fetch error handling in BitBake, let's just print the text of the exception and then we know we have shown something to the user. Additionally, we were only catching FetchException here but there are several other classes of exception that the fetcher can raise (e.g. MalformedUrl); catch the parent BBFetchException class instead so we avoid tracebacks for those other classes as well. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-extended')
0 files changed, 0 insertions, 0 deletions