From b55f765ae46eb08d9c92a862c6bc4b9044c0b42d Mon Sep 17 00:00:00 2001 From: Richard Purdie Date: Thu, 30 Apr 2020 20:55:39 +0100 Subject: abi_version/staging: Bump versions to force rebuild after sstate corruption A "broken" buildtools-extended-tarball has been released into the wild where it is optimising binaries for the host processsor. This is fine in local usage but in a non-homogeneous cluster like our autobuilder, this results in SIGILL on other machines when the sstate is shared amongst them and is painful to debug. The buildtools tarball has been fixed but we need to invalidate the hash equivalence and sstate data. This change does that. Adding to OE-Core rather than autobuilder local changes as its good to illustrate how to do this and the issue is potentially wider than just Yocto Project infrastructure. (From OE-Core rev: 23cdfa9eb23146a69edb77a83ef03719a62ddaae) Signed-off-by: Richard Purdie --- meta/conf/abi_version.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'meta/conf/abi_version.conf') diff --git a/meta/conf/abi_version.conf b/meta/conf/abi_version.conf index 2bdc55695b..e04343b47c 100644 --- a/meta/conf/abi_version.conf +++ b/meta/conf/abi_version.conf @@ -12,4 +12,4 @@ OELAYOUT_ABI = "12" # a reset of the equivalence, for example when reproducibility issues break the # existing match data. Distros can also append to this value for the same effect. # -HASHEQUIV_HASH_VERSION = "1" +HASHEQUIV_HASH_VERSION = "3" -- cgit v1.2.3-54-g00ecf