From mboxrd@z Thu Jan  1 00:00:00 1970
X-GM-THRID: 6742861381616271360
Date: Tue, 1 Oct 2019 09:14:54 -0700 (PDT)
From: vijai kumar <vijaikumar.kanagarajan@gmail.com>
To: isar-users <isar-users@googlegroups.com>
Message-Id: <58f6a558-d743-418f-a301-33590915dea3@googlegroups.com>
In-Reply-To: <20191001154552.vu33jzro2zwjfyr3@yssyq.m.ilbers.de>
References: <20191001154552.vu33jzro2zwjfyr3@yssyq.m.ilbers.de>
Subject: Re: gpg: can't connect to the agent: IPC connect call failed
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_2105_1475418570.1569946494609"
X-Google-Token: EP72zewFTnHENNn0eMI0
X-Google-IP: 192.94.34.34
X-TUID: xbTa4FJd5Baq

------=_Part_2105_1475418570.1569946494609
Content-Type: multipart/alternative; 
	boundary="----=_Part_2106_837371291.1569946494609"

------=_Part_2106_837371291.1569946494609
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Hello Baurzhan,

Which fixes are we talking about here?

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. 
>

------=_Part_2106_837371291.1569946494609
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<div dir="ltr">Hello Baurzhan,<div><br></div><div>Which fixes are we talking about here?</div><div><br></div><div>Thanks,</div><div>Vijai Kumar K<br><br>On Tuesday, October 1, 2019 at 9:15:55 PM UTC+5:30, Baurzhan Ismagulov wrote:<blockquote class="gmail_quote" style="margin: 0;margin-left: 0.8ex;border-left: 1px #ccc solid;padding-left: 1ex;">Hello,
<br>
<br>after the signing fixes, I occasionally see the following error messages from
<br>isar-bootstrap-target:
<br>
<br>gpg: can&#39;t connect to the agent: IPC connect call failed
<br>
<br>The build fails. This happens presumably during apt-key in the target chroot.
<br>
<br>Has anyone seen this?
<br>
<br>With kind regards,
<br>Baurzhan.
<br></blockquote></div></div>
------=_Part_2106_837371291.1569946494609--

------=_Part_2105_1475418570.1569946494609--