From: Henning Schild <henning.schild@siemens.com>
To: <vijaikumar.kanagarajan@gmail.com>
Cc: <isar-users@googlegroups.com>, <claudius.heine.ext@siemens.com>,
<jan.kiszka@siemens.com>,
Vijai Kumar K <Vijaikumar_Kanagarajan@mentor.com>
Subject: Re: [PATCH] export GNUGPHOME for reprepro
Date: Thu, 1 Aug 2019 13:12:19 +0200 [thread overview]
Message-ID: <20190801131219.33274775@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20190725071504.24037-1-Vijaikumar_Kangarajan@mentor.com>
Am Thu, 25 Jul 2019 12:45:04 +0530
schrieb <vijaikumar.kanagarajan@gmail.com>:
> From: Vijai Kumar K <Vijaikumar_Kanagarajan@mentor.com>
>
> reprepro doesnot know about GNUPGHOME. If you trigger package feed
> creation in a machine that has GNUPGHOME set, reprepro would not
> know that it should use the new location and might use the keys it
> find in the default ~/.gnupg directory.
>
> Make GNUPGHOME available for reprepro.
>
> Signed-off-by: Vijai Kumar K <Vijaikumar_Kanagarajan@mentor.com>
> ---
> meta/classes/base-apt-helper.bbclass | 4 ++++
> meta/classes/dpkg-base.bbclass | 3 +++
> meta/recipes-devtools/base-apt/base-apt.bb | 3 +++
> meta/recipes-devtools/isar-apt/isar-apt.bb | 3 +++
> scripts/isar-buildenv-internal | 3 +++
> 5 files changed, 16 insertions(+)
>
> diff --git a/meta/classes/base-apt-helper.bbclass
> b/meta/classes/base-apt-helper.bbclass index ba768da..a8f2a41 100644
> --- a/meta/classes/base-apt-helper.bbclass
> +++ b/meta/classes/base-apt-helper.bbclass
> @@ -30,6 +30,10 @@ populate_base_apt() {
> compare_pkg_md5sums "$package" "$isar_package" &&
> continue fi
>
> + if [ ! -z ${GNUPGHOME} ]; then
> + export GNUPGHOME=${GNUPGHOME}
> + fi
> +
> # Check if this package is already in base-apt
> isar_package=$(find ${REPO_BASE_DIR}/${BASE_DISTRO} -name
> $base_name) if [ -n "$isar_package" ]; then
> diff --git a/meta/classes/dpkg-base.bbclass
> b/meta/classes/dpkg-base.bbclass index 3e6ba8c..da13f86 100644
> --- a/meta/classes/dpkg-base.bbclass
> +++ b/meta/classes/dpkg-base.bbclass
> @@ -120,6 +120,9 @@ repo_clean() {
>
> # Install package to Isar-apt
> do_deploy_deb() {
> + if [ ! -z ${GNUPGHOME} ]; then
> + export GNUPGHOME=${GNUPGHOME}
> + fi
> repo_clean
> reprepro -b ${REPO_ISAR_DIR}/${DISTRO} \
> --dbdir ${REPO_ISAR_DB_DIR}/${DISTRO} \
> diff --git a/meta/recipes-devtools/base-apt/base-apt.bb
> b/meta/recipes-devtools/base-apt/base-apt.bb index 1c0b4c6..ca40b6c
> 100644 --- a/meta/recipes-devtools/base-apt/base-apt.bb
> +++ b/meta/recipes-devtools/base-apt/base-apt.bb
> @@ -28,6 +28,9 @@ do_cache_config() {
> path_databases="${REPO_BASE_DB_DIR}/${BASE_DISTRO}"
>
> if [ ! -d "${path_databases}" ]; then
> + if [ ! -z ${GNUPGHOME} ]; then
> + export GNUPGHOME=${GNUPGHOME}
> + fi
> reprepro -b ${path_cache} \
> --dbdir ${path_databases} \
> export ${BASE_DISTRO_CODENAME}
> diff --git a/meta/recipes-devtools/isar-apt/isar-apt.bb
> b/meta/recipes-devtools/isar-apt/isar-apt.bb index a959691..8f517fe
> 100644 --- a/meta/recipes-devtools/isar-apt/isar-apt.bb
> +++ b/meta/recipes-devtools/isar-apt/isar-apt.bb
> @@ -20,6 +20,9 @@ do_cache_config() {
> path_databases="${REPO_ISAR_DB_DIR}/${DISTRO}"
>
> if [ ! -d "${path_databases}" ]; then
> + if [ ! -z ${GNUPGHOME} ]; then
> + export GNUPGHOME=${GNUPGHOME}
> + fi
> reprepro -b ${path_cache} \
> --dbdir ${path_databases} \
> export ${DEBDISTRONAME}
> diff --git a/scripts/isar-buildenv-internal
> b/scripts/isar-buildenv-internal index 2476d90..7637d41 100755
> --- a/scripts/isar-buildenv-internal
> +++ b/scripts/isar-buildenv-internal
> @@ -67,4 +67,7 @@ BBPATH="${BUILDDIR}"
> export BBPATH
>
> BB_ENV_EXTRAWHITE="BUILDDIR ISARROOT http_proxy https_proxy
> ftp_proxy no_proxy" +if [ ! -z ${GNUPGHOME} ]; then
> + BB_ENV_EXTRAWHITE="${BB_ENV_EXTRAWHITE} GNUPGHOME"
> +fi
Why did you go for conditional append for that one, while the others
are unconditional?
Henning
> export BB_ENV_EXTRAWHITE
next prev parent reply other threads:[~2019-08-01 11:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 7:15 vijaikumar.kanagarajan
2019-07-25 7:25 ` Henning Schild
2019-07-25 8:59 ` Vijai Kumar K
2019-07-25 7:35 ` Claudius Heine
2019-07-25 9:08 ` [PATCH v2] " vijaikumar.kanagarajan
2019-07-25 9:10 ` Jan Kiszka
2019-07-25 9:15 ` Vijai Kumar K
2019-08-01 11:12 ` Henning Schild [this message]
2019-08-01 11:23 ` [PATCH] " vijai kumar
2019-08-01 11:34 ` vijai kumar
2019-08-01 11:38 ` Henning Schild
2019-08-01 11:42 ` vijai kumar
2019-08-01 11:48 ` Baurzhan Ismagulov
2019-08-01 11:52 ` Henning Schild
2019-08-01 12:09 ` Baurzhan Ismagulov
2019-08-05 10:58 ` [PATCH v2] " vijaikumar.kanagarajan
2019-08-06 8:35 ` [PATCH v2] export GNUPGHOME " Baurzhan Ismagulov
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=20190801131219.33274775@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=Vijaikumar_Kanagarajan@mentor.com \
--cc=claudius.heine.ext@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=vijaikumar.kanagarajan@gmail.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