summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorPaul Eggleton <paul.eggleton@linux.intel.com>2016-12-13 20:07:00 +1300
committerRichard Purdie <richard.purdie@linuxfoundation.org>2016-12-14 12:25:06 +0000
commit3fa98e19d5817ae7cf9607e4cda9cf2a808c320d (patch)
tree68bc4522a5388c1a968614efc40d038ddab40b00
parent209a19ce1666d55bf300a4bee80ed4f5eedc3691 (diff)
downloadpoky-3fa98e19d5817ae7cf9607e4cda9cf2a808c320d.tar.gz
bitbake: data_smart: fix resetting of reference on variablehistory
There is no "datasmart" member, only dataroot. This dates back to the original implementation of variable history support - it's surprising we haven't noticed the issue until now, but I guess it's rare to change a copy of a datastore in a manner which using the old reference would cause an issue. (Bitbake rev: febd5534b07edfdef15cedb0578730c582c7373f) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--bitbake/lib/bb/data_smart.py2
1 files changed, 1 insertions, 1 deletions
diff --git a/bitbake/lib/bb/data_smart.py b/bitbake/lib/bb/data_smart.py
index be43eb9be3..17768c8f4b 100644
--- a/bitbake/lib/bb/data_smart.py
+++ b/bitbake/lib/bb/data_smart.py
@@ -844,7 +844,7 @@ class DataSmart(MutableMapping):
844 data = DataSmart() 844 data = DataSmart()
845 data.dict["_data"] = self.dict 845 data.dict["_data"] = self.dict
846 data.varhistory = self.varhistory.copy() 846 data.varhistory = self.varhistory.copy()
847 data.varhistory.datasmart = data 847 data.varhistory.dataroot = data
848 data.inchistory = self.inchistory.copy() 848 data.inchistory = self.inchistory.copy()
849 849
850 data._tracking = self._tracking 850 data._tracking = self._tracking