summaryrefslogtreecommitdiffstats
path: root/lib/bb/fetch2/npm.py
diff options
context:
space:
mode:
authorPaul Eggleton <paul.eggleton@linux.intel.com>2017-08-31 11:30:46 +1200
committerRichard Purdie <richard.purdie@linuxfoundation.org>2017-08-31 17:42:08 +0100
commitf120355eaec4571ba6d60fc5f7ae9e1f31d846d1 (patch)
tree156f3c10b0340fa742fe5f9b5fd293e71f9580a5 /lib/bb/fetch2/npm.py
parentcc8b4c81bb589fb70774a0151f87a8d277f40f06 (diff)
downloadbitbake-contrib-f120355eaec4571ba6d60fc5f7ae9e1f31d846d1.tar.gz
bitbake-contrib-f120355eaec4571ba6d60fc5f7ae9e1f31d846d1.tar.bz2
bitbake-contrib-f120355eaec4571ba6d60fc5f7ae9e1f31d846d1.zip
cooker: ensure we can run buildFileInternal() after cache is populated
If you run some other operations that result in the cache being populated, and then call buildFileInternal(), then you can end up in a situation where the cache already contains information about the recipe. For example in OE this can now happen when you use devtool upgrade. Normally this doesn't cause any problems, unless you have a non-absolute path in BBLAYERS - in buildFileInternal() we are calling matchfile() which will convert the filename to absolute, but later when taskdata goes to find the providers of the recipe it finds the non-absolute path, sets up the task information using this and then the runqueue can't find any tasks matching the absolute path. To fix this, back out the optimisation I did earlier in bitbake rev ba53e067a2d448dd63b4ca252557ce98aa8e6321 to avoid calling parseConfiguration() again, which is unfortunate but does result in the cached information being that causes the problem being cleared out. This fixes "Task do_unpack does not exist for target ..." running devtool upgrade within intel-iot-refkit. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'lib/bb/fetch2/npm.py')
0 files changed, 0 insertions, 0 deletions