From: vijai kumar <vijaikumar.kanagarajan@gmail.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH v2] base-apt: Use gpg keyid instead of yes
Date: Sat, 2 Nov 2019 22:07:04 +0530 [thread overview]
Message-ID: <CALLGG_LV91YsS-PrjTkNng1NxgNzgj59MXxYFTZ_zXoZZ6p2nA@mail.gmail.com> (raw)
In-Reply-To: <20191102155725.ecot7nhc4f3pqxck@yssyq.m.ilbers.de>
[-- Attachment #1: Type: text/plain, Size: 2082 bytes --]
Sure Baurzhan. I'm on travel. I'll look into it first thing Monday morning.
Thanks,
Vijai Kumar K
On Sat 2 Nov, 2019, 9:27 PM Baurzhan Ismagulov, <ibr@radix50.net> wrote:
> Hello Vijai Kumar,
>
> On Tue, Oct 15, 2019 at 02:47:23PM +0530, vijaikumar.kanagarajan@gmail.com
> wrote:
> > When using "SignWith: yes", reprepro uses the default gpg key
> > of the system to sign the repo. The default gpg key might be
> > different from what is specified in BASE_REPO_KEY, resulting
> > in using a wrong key for signing.
> >
> > Derive and use the keyid from the keyfile supplied instead of
> > a generic yes option.
>
> I'm experiencing the problems below, could you please have a look?
>
> http://ci.isar-build.org:8080/job/isar_ibr_next/lastFailedBuild/consoleFull
>
> bitbake -v -c cache_base_repo multiconfig:qemuarm-stretch:isar-image-base
> multiconfig:qemuarm64-stretch:isar-image-base
> multiconfig:qemuamd64-stretch:isar-image-base
> multiconfig:qemuarm-buster:isar-image-base
> ...
> ERROR: mc:qemuarm-buster:base-apt-1.0-r0 do_cache_config: Function failed:
> repo_config (log file is located at
> /workspace/build/isar_ibr_next/12/build/tmp/work/debian-buster-armhf/base-apt/1.0-r0/temp/log.do_cache_config.16781)
> ...
> | + export GNUPGHOME=/tmp/tmp.laEgOqLEko
> | + reprepro -b
> /workspace/build/isar_ibr_next/12/build/downloads/base-apt/debian-buster/apt/debian
> --dbdir
> /workspace/build/isar_ibr_next/12/build/downloads/base-apt/debian-buster/db/debian
> export buster
> | Error parsing
> /workspace/build/isar_ibr_next/12/build/downloads/base-apt/debian-buster/apt/debian/conf/distributions,
> line 4, column 12: Missing value for SignWith field.
>
> With kind regards,
> Baurzhan.
>
> --
> 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 on the web visit
> https://groups.google.com/d/msgid/isar-users/20191102155725.ecot7nhc4f3pqxck%40yssyq.m.ilbers.de
> .
>
[-- Attachment #2: Type: text/html, Size: 3076 bytes --]
next prev parent reply other threads:[~2019-11-02 16:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-27 21:11 [PATCH] " 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 [this message]
2019-11-05 10:33 ` [PATCH] meta/base-apt: Fix build issue with CI vijaikumar.kanagarajan
2019-11-05 18:10 ` vijai kumar
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=CALLGG_LV91YsS-PrjTkNng1NxgNzgj59MXxYFTZ_zXoZZ6p2nA@mail.gmail.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