diff options
| author |   Paul Eggleton <paul.eggleton@linux.intel.com> | 2016-12-13 20:07:00 +1300 |
|---|---|---|
| committer |   Richard Purdie <richard.purdie@linuxfoundation.org> | 2016-12-14 09:54:48 +0000 |
| commit | febd5534b07edfdef15cedb0578730c582c7373f (patch) | |
| tree | 789764bde6a78966415cbc292268e69877212dce | |
| parent | b65a8193368ffa1d15af24a6acde8dce6bd4d383 (diff) | |
| download | bitbake-contrib-febd5534b07edfdef15cedb0578730c582c7373f.tar.gz | |
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.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
| -rw-r--r-- | lib/bb/data_smart.py | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/lib/bb/data_smart.py b/lib/bb/data_smart.py index be43eb9be..17768c8f4 100644 --- a/lib/bb/data_smart.py +++ b/lib/bb/data_smart.py @@ -844,7 +844,7 @@ class DataSmart(MutableMapping): data = DataSmart() data.dict["_data"] = self.dict data.varhistory = self.varhistory.copy() - data.varhistory.datasmart = data + data.varhistory.dataroot = data data.inchistory = self.inchistory.copy() data._tracking = self._tracking |