From: Vijai Kumar K <vijaikumar.kanagarajan@gmail.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: vijai kumar <vijaikumar.kanagarajan@gmail.com>,
isar-users <isar-users@googlegroups.com>
Subject: Re: gpg: can't connect to the agent: IPC connect call failed
Date: Tue, 1 Oct 2019 23:11:07 +0530 [thread overview]
Message-ID: <20191001174106.GA11738@lightning> (raw)
In-Reply-To: <bd71067e-b8c6-e7c0-11e0-eb2ce3845283@siemens.com>
On Tue, Oct 01, 2019 at 07:22:03PM +0200, Jan Kiszka wrote:
> On 01.10.19 18:55, vijai kumar wrote:
> > Thanks for the clarification Jan. I see them in ibr/next.
> >
> > I have not faced any issues with next branch till now. Let me see ibr/next.
>
> It's actually in the official "next" now.
>
> Jan
Yes. Sorry, My bad. I didn't update my fork yet.
Thanks,
Vijai Kumar K
>
> >
> > - Vijai Kumar K
> >
> > On Tuesday, October 1, 2019 at 10:13:32 PM UTC+5:30, Jan Kiszka wrote:
> >
> > On 01.10.19 18:14, vijai kumar wrote:
> > > Hello Baurzhan,
> > >
> > > Which fixes are we talking about here?
> >
> > isar-bootstrap: Add gnupg also when using BASE_REPO_KEY
> > isar-bootstrap: Fix keyring generation
> > isar-bootstrap: Install DISTRO_BOOTSTRAP_KEYS
> >
> > etc. They are in next now. We were using them internally already.
> >
> > Jan
> >
> > >
> > > Thanks,
> > > Vijai Kumar K
> > >
> > > On Tuesday, October 1, 2019 at 9:15:55 PM UTC+5:30, Baurzhan Ismagulov
> > wrote:
> > >
> > > � � Hello,
> > >
> > > � � after the signing fixes, I occasionally see the following error
> > messages from
> > > � � isar-bootstrap-target:
> > >
> > > � � gpg: can't connect to the agent: IPC connect call failed
> > >
> > > � � The build fails. This happens presumably during apt-key in the target
> > chroot.
> > >
> > > � � Has anyone seen this?
> > >
> > > � � 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-...@googlegroups.com <javascript:>
> > > <mailto:isar-users+unsubscribe@googlegroups.com <javascript:>>.
> > > To view this discussion on the web visit
> > >
> > https://groups.google.com/d/msgid/isar-users/58f6a558-d743-418f-a301-33590915dea3%40googlegroups.com
> > <https://groups.google.com/d/msgid/isar-users/58f6a558-d743-418f-a301-33590915dea3%40googlegroups.com>
> >
> > >
> > <https://groups.google.com/d/msgid/isar-users/58f6a558-d743-418f-a301-33590915dea3%40googlegroups.com?utm_medium=email&utm_source=footer
> > <https://groups.google.com/d/msgid/isar-users/58f6a558-d743-418f-a301-33590915dea3%40googlegroups.com?utm_medium=email&utm_source=footer>>.
> >
> > -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE
> > Corporate Competence Center Embedded Linux
> >
> > --
> > 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
> > <mailto:isar-users+unsubscribe@googlegroups.com>.
> > To view this discussion on the web visit https://groups.google.com/d/msgid/isar-users/5d63cedf-bbd7-456f-a5f8-84beebe8ffab%40googlegroups.com <https://groups.google.com/d/msgid/isar-users/5d63cedf-bbd7-456f-a5f8-84beebe8ffab%40googlegroups.com?utm_medium=email&utm_source=footer>.
>
> --
> Siemens AG, Corporate Technology, CT RDA IOT SES-DE
> Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2019-10-01 17:41 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
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 [this message]
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=20191001174106.GA11738@lightning \
--to=vijaikumar.kanagarajan@gmail.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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