summaryrefslogtreecommitdiffstats
path: root/bitbake
diff options
context:
space:
mode:
authorJoshua Watt <JPEWhacker@gmail.com>2020-06-19 13:41:32 -0500
committerRichard Purdie <richard.purdie@linuxfoundation.org>2020-06-19 23:18:18 +0100
commitfced0b8d7c852e52606fa8da321211a98a1dfaea (patch)
tree95c7af9ddef6cf6d13b19879dcaae06d66c65ad6 /bitbake
parent29bfa17d6cab31dbf8f1d12e473ef83dd9e92519 (diff)
downloadpoky-fced0b8d7c852e52606fa8da321211a98a1dfaea.tar.gz
bitbake: cache: Bump cache version
The layout of the cache data hasn't changed, but the cache has now been split into different files for multiconfig. If a user pulls in these changes, it's possible that their base cache will still contain the combined multiconfig cache entries, which are now unexpected and generate errors like: Unexpected multiconfig: foo Bumping the version fixes this since the old cache data won't be considered valid anymore. (Bitbake rev: 1082188ce633ec6891c961d726f584b3f1259941) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake')
-rw-r--r--bitbake/lib/bb/cache.py2
1 files changed, 1 insertions, 1 deletions
diff --git a/bitbake/lib/bb/cache.py b/bitbake/lib/bb/cache.py
index c1e08511ba..b819a0c2da 100644
--- a/bitbake/lib/bb/cache.py
+++ b/bitbake/lib/bb/cache.py
@@ -26,7 +26,7 @@ import re
26 26
27logger = logging.getLogger("BitBake.Cache") 27logger = logging.getLogger("BitBake.Cache")
28 28
29__cache_version__ = "152" 29__cache_version__ = "153"
30 30
31def getCacheFile(path, filename, mc, data_hash): 31def getCacheFile(path, filename, mc, data_hash):
32 mcspec = '' 32 mcspec = ''