public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: vijai kumar <vijaikumar.kanagarajan@gmail.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH] meta/base-apt: Fix build issue with CI
Date: Tue, 5 Nov 2019 10:10:27 -0800 (PST)	[thread overview]
Message-ID: <c3446580-171c-4bcd-9c45-192e17afa762@googlegroups.com> (raw)
In-Reply-To: <20191105103314.11454-1-Vijaikumar_Kangarajan@mentor.com>


[-- Attachment #1.1: Type: text/plain, Size: 2060 bytes --]

The build succeeded.

Thanks,
Vijai Kumar K


On Tuesday, November 5, 2019 at 4:03:27 PM UTC+5:30, vijai kumar wrote:
>
> From: Vijai Kumar K <Vijaikumar_Kanagarajan@mentor.com> 
>
> CI triggers the build in a chrooted environment with userspec 
> option set to host user. GPG commands would fail since we donot have 
> access to the $HOME folder in chroot. 
>
> Make GNUPGHOME available to avoid failures due to permission issues. 
>
> Signed-off-by: Vijai Kumar K <Vijaikumar_Kanagarajan@mentor.com> 
> --- 
>
> Hi Baurzhan, 
>
> This patch should fix the issue we are facing in CI. 
>
> There is a job running successfully with this patchset at   
> http://ci.isar-build.org:8080/job/isar_vkk_devel/10/consoleFull 
>
>
> Thanks, 
> Vijai Kumar K 
>
>  meta/recipes-devtools/base-apt/base-apt.bb | 7 ++++--- 
>  1 file changed, 4 insertions(+), 3 deletions(-) 
>
> diff --git a/meta/recipes-devtools/base-apt/base-apt.bb 
> b/meta/recipes-devtools/base-apt/base-apt.bb 
> index 42ff782..9a0f7c8 100644 
> --- a/meta/recipes-devtools/base-apt/base-apt.bb 
> +++ b/meta/recipes-devtools/base-apt/base-apt.bb 
> @@ -14,6 +14,10 @@ do_cache_config[lockfiles] = 
> "${REPO_BASE_DIR}/isar.lock" 
>  # Generate reprepro config for current distro if it doesn't exist. Once 
> it's 
>  # generated, this task should do nothing. 
>  repo_config() { 
> +    if [ -n "${GNUPGHOME}" ]; then 
> +        export GNUPGHOME="${GNUPGHOME}" 
> +    fi 
> + 
>      if [ ! -e "${CACHE_CONF_DIR}/distributions" ]; then 
>          sed -e "s#{CODENAME}#"${BASE_DISTRO_CODENAME}"#g" \ 
>              ${WORKDIR}/distributions.in > 
> ${CACHE_CONF_DIR}/distributions 
> @@ -32,9 +36,6 @@ repo_config() { 
>      path_databases="${REPO_BASE_DB_DIR}/${BASE_DISTRO}" 
>   
>      if [ ! -d "${path_databases}" ]; then 
> -        if [ -n "${GNUPGHOME}" ]; then 
> -            export GNUPGHOME="${GNUPGHOME}" 
> -        fi 
>          reprepro -b ${path_cache} \ 
>                   --dbdir ${path_databases} \ 
>                   export ${BASE_DISTRO_CODENAME} 
> -- 
> 2.17.1 
>
>

[-- Attachment #1.2: Type: text/html, Size: 6152 bytes --]

  reply	other threads:[~2019-11-05 18:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-27 21:11 [PATCH] base-apt: Use gpg keyid instead of yes vijaikumar.kanagarajan
2019-09-30  6:17 ` Jan Kiszka
2019-09-30  8:42   ` Vijai Kumar K
2019-09-30  8:51     ` vijai kumar
2019-10-14 16:38   ` Henning Schild
2019-10-15  9:17     ` [PATCH v2] " vijaikumar.kanagarajan
2019-10-15  9:19       ` vijai kumar
2019-10-23  7:24         ` Vijai Kumar K
2019-11-02 15:57       ` Baurzhan Ismagulov
2019-11-02 16:37         ` vijai kumar
2019-11-05 10:33           ` [PATCH] meta/base-apt: Fix build issue with CI vijaikumar.kanagarajan
2019-11-05 18:10             ` vijai kumar [this message]
2019-11-19 16:41             ` Baurzhan Ismagulov
2019-11-19 16:40       ` [PATCH v2] base-apt: Use gpg keyid instead of yes 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=c3446580-171c-4bcd-9c45-192e17afa762@googlegroups.com \
    --to=vijaikumar.kanagarajan@gmail.com \
    --cc=isar-users@googlegroups.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