From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Subject: Re: gpg: can't connect to the agent: IPC connect call failed
Date: Tue, 1 Oct 2019 20:27:18 +0200 [thread overview]
Message-ID: <20191001182717.7ydrjqukdksmcy4m@yssyq.m.ilbers.de> (raw)
In-Reply-To: <4667c894-f9bc-01a0-a93c-d32f7e9034e8@siemens.com>
On Tue, Oct 01, 2019 at 06:00:21PM +0200, Jan Kiszka wrote:
> Not yet, at least not in kas-isar. Buster or stretch host? We are back to
> stretch (for configuration management reasons in kas), but we will move
> forward again soon. Is this for arbitrary targets or just cross
> (qemu-based)?
Thanks for the quick responses. The chroot is stretch. Occurred 6 times since
2019-09-20. The target is always rpi-stretch.
The question of commits is also a good one. The earliest commit exhibiting the
problem is:
dd1ddaa buildchroot: Properly deploy the build result
It contains:
dfdeff3 isar-bootstrap: Install DISTRO_BOOTSTRAP_KEYS
0d62fd1 isar-bootstrap: Fix keyring generation
The problem has occurred with and without the following:
eecd7a3 isar-bootstrap: Install DISTRO_BOOTSTRAP_KEYS
a6a48e6 isar-bootstrap: Fix keyring generation
3895266 isar-bootstrap: Add gnupg also when using BASE_REPO_KEY
01acc39 isar-bootstrap: Switch to gnupg as dependency, rather than obsolete gnupg2
With kind regards,
Baurzhan.
next prev parent reply other threads:[~2019-10-01 18:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-01 15:45 Baurzhan Ismagulov
2019-10-01 16:00 ` Jan Kiszka
2019-10-01 18:27 ` Baurzhan Ismagulov [this message]
2019-10-01 16:14 ` vijai kumar
2019-10-01 16:43 ` Jan Kiszka
2019-10-01 16:55 ` vijai kumar
2019-10-01 17:22 ` Jan Kiszka
2019-10-01 17:41 ` Vijai Kumar K
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=20191001182717.7ydrjqukdksmcy4m@yssyq.m.ilbers.de \
--to=ibr@radix50.net \
--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