[PATCH 1/1] bitbake: exclude GNUPGHOME from signatures

[Felix Moessbauer]

The GNUPGHOME can be passed from the calling environment and points to
an absolute path. This makes all sstate artifacts that transitively
depend on this variable non reproducible (when setting GNUPGHOME).

Signed-off-by: Felix Moessbauer <felix.mo...@siemens.com>
---
meta/conf/bitbake.conf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index be7d4801..cbe284df 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -101,7 +101,7 @@ REPO_BASE_DB_DIR = "${DEPLOY_DIR}/base-apt/${DISTRO}/db"
BB_SIGNATURE_HANDLER ?= "OEEquivHash"
BB_HASHSERVE ??= "auto"
BB_HASHEXCLUDE_ISAR ?= "CCACHE_DEBUG LAYERDIR_core SCRIPTSDIR TOPDIR ISAR_BUILD_UUID \
- RUN_PRIVILEGED_CMD UNSHARE_SUBUID_BASE"
+ RUN_PRIVILEGED_CMD UNSHARE_SUBUID_BASE GNUPGHOME"
BB_HASHEXCLUDE_COMMON ?= "TMPDIR FILE PATH PWD BB_TASKHASH BBPATH BBSERVER DL_DIR \
THISDIR FILESEXTRAPATHS FILE_DIRNAME HOME LOGNAME SHELL \
USER FILESPATH STAGING_DIR_HOST STAGING_DIR_TARGET COREBASE PRSERV_HOST \
--
2.55.0