From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Cc: Uladzimir Bely <ubely@ilbers.de>
Subject: [PATCH] dpkg: Do not warn about GIT_PROXY_COMMAND exports
Date: Sat, 16 Sep 2023 15:49:03 +0530 [thread overview]
Message-ID: <f818a8eb-f0ae-4b61-9f8f-12223770842d@siemens.com> (raw)
From: Jan Kiszka <jan.kiszka@siemens.com>
Latest bitbake now forwards this, causing our export check to raise a
false alarm.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
Visible when using kas-container, thus also with the recent kas patches.
meta/classes/dpkg.bbclass | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/classes/dpkg.bbclass b/meta/classes/dpkg.bbclass
index c596adbf..b5d12481 100644
--- a/meta/classes/dpkg.bbclass
+++ b/meta/classes/dpkg.bbclass
@@ -61,6 +61,7 @@ dpkg_runbuild() {
[ "${var}" = "FTP_PROXY" ] && continue
[ "${var}" = "no_proxy" ] && continue
[ "${var}" = "NO_PROXY" ] && continue
+ [ "${var}" = "GIT_PROXY_COMMAND" ] && continue
bbwarn "Export of '${line}' detected, please migrate to templates"
done
--
2.35.3
next reply other threads:[~2023-09-16 10:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-16 10:19 Jan Kiszka [this message]
2023-09-22 4:26 ` Uladzimir Bely
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=f818a8eb-f0ae-4b61-9f8f-12223770842d@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=ubely@ilbers.de \
/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