public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'Clara Kowalsky' via isar-users" <isar-users@googlegroups.com>
To: isar-users@googlegroups.com
Cc: Clara Kowalsky <clara.kowalsky@siemens.com>,
	Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: [PATCH v2 4/6] bitbake.conf: explicitly exclude export and func from signatures
Date: Tue, 17 Nov 2026 15:41:07 +0100	[thread overview]
Message-ID: <20261117144109.2417395-5-clara.kowalsky@siemens.com> (raw)
In-Reply-To: <20261117144109.2417395-1-clara.kowalsky@siemens.com>

BitBake v2.18 includes commit ddb97b7c5e40 ("bitbake: fix issue with
varflag exclusion") which changes BB_SIGNATURE_EXCLUDE_FLAGS to match
complete flag names instead of substrings.

Isar lists export_func, which previously implicitly excluded export and
func. With the updated matching, both flags must be added to the
exclusion list to keep them out of the task signatures.

Signed-off-by: Clara Kowalsky <clara.kowalsky@siemens.com>
Tested-by: Felix Moessbauer <felix.moessbauer@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 c31719b8..75239744 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -121,7 +121,7 @@ BB_HASHCONFIG_IGNORE_VARS ?= "${BB_HASHEXCLUDE_COMMON} DATE TIME SSH_AGENT_PID \
     BB_SETSCENE_ENFORCE BB_CMDLINE BB_SERVER_TIMEOUT"
 BB_SIGNATURE_EXCLUDE_FLAGS ?= "doc deps depends \
     lockfiles vardepsexclude vardeps vardepvalue vardepvalueexclude \
-    file-checksums python task nostamp \
+    file-checksums python task nostamp export func \
     sstate-lockfile-shared prefuncs postfuncs export_func deptask rdeptask \
     recrdeptask nodeprrecs stamp-extra-info sstate-outputdirs filename lineno \
     progress mcdepends number_threads"
-- 
2.56.1

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/20261117144109.2417395-5-clara.kowalsky%40siemens.com.

  parent reply	other threads:[~2026-11-17 14:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-17 14:41 [PATCH v2 0/6] Update BitBake in Isar 'Clara Kowalsky' via isar-users
2026-11-17 14:41 ` [PATCH v2 1/6] base: replace BitBake's outdated persist_data 'Clara Kowalsky' via isar-users
2026-11-17 14:41 ` [PATCH v2 2/6] isar-events: preserve cleanup for default multiconfig 'Clara Kowalsky' via isar-users
2026-11-17 14:41 ` [PATCH v2 3/6] wic: run the Python driver outside the imaging chroot 'Clara Kowalsky' via isar-users
2026-11-18 12:25   ` 'Moessbauer, Felix' via isar-users
2026-11-18 12:47   ` 'Moessbauer, Felix' via isar-users
2026-11-17 14:41 ` 'Clara Kowalsky' via isar-users [this message]
2026-11-17 14:41 ` [PATCH v2 5/6] meta: add missing whitespace around assignment operators 'Clara Kowalsky' via isar-users
2026-11-17 14:41 ` [PATCH v2 6/6] bitbake: update to branch 2.18, tag yocto-6.0.4 'Clara Kowalsky' via isar-users

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20261117144109.2417395-5-clara.kowalsky@siemens.com \
    --to=isar-users@googlegroups.com \
    --cc=clara.kowalsky@siemens.com \
    --cc=felix.moessbauer@siemens.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox