* gpg: can't connect to the agent: IPC connect call failed
@ 2019-10-01 15:45 Baurzhan Ismagulov
2019-10-01 16:00 ` Jan Kiszka
2019-10-01 16:14 ` vijai kumar
0 siblings, 2 replies; 8+ messages in thread
From: Baurzhan Ismagulov @ 2019-10-01 15:45 UTC (permalink / raw)
To: isar-users
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.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: gpg: can't connect to the agent: IPC connect call failed
2019-10-01 15:45 gpg: can't connect to the agent: IPC connect call failed Baurzhan Ismagulov
@ 2019-10-01 16:00 ` Jan Kiszka
2019-10-01 18:27 ` Baurzhan Ismagulov
2019-10-01 16:14 ` vijai kumar
1 sibling, 1 reply; 8+ messages in thread
From: Jan Kiszka @ 2019-10-01 16:00 UTC (permalink / raw)
To: isar-users
On 01.10.19 17:45, 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?
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)?
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: gpg: can't connect to the agent: IPC connect call failed
2019-10-01 15:45 gpg: can't connect to the agent: IPC connect call failed Baurzhan Ismagulov
2019-10-01 16:00 ` Jan Kiszka
@ 2019-10-01 16:14 ` vijai kumar
2019-10-01 16:43 ` Jan Kiszka
1 sibling, 1 reply; 8+ messages in thread
From: vijai kumar @ 2019-10-01 16:14 UTC (permalink / raw)
To: isar-users
[-- Attachment #1.1: Type: text/plain, Size: 497 bytes --]
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.
>
[-- Attachment #1.2: Type: text/html, Size: 726 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: gpg: can't connect to the agent: IPC connect call failed
2019-10-01 16:14 ` vijai kumar
@ 2019-10-01 16:43 ` Jan Kiszka
2019-10-01 16:55 ` vijai kumar
0 siblings, 1 reply; 8+ messages in thread
From: Jan Kiszka @ 2019-10-01 16:43 UTC (permalink / raw)
To: vijai kumar, isar-users
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-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/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>.
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: gpg: can't connect to the agent: IPC connect call failed
2019-10-01 16:43 ` Jan Kiszka
@ 2019-10-01 16:55 ` vijai kumar
2019-10-01 17:22 ` Jan Kiszka
0 siblings, 1 reply; 8+ messages in thread
From: vijai kumar @ 2019-10-01 16:55 UTC (permalink / raw)
To: isar-users
[-- Attachment #1.1: Type: text/plain, Size: 1840 bytes --]
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.
- 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?utm_medium=email&utm_source=footer>.
>
> --
> Siemens AG, Corporate Technology, CT RDA IOT SES-DE
> Corporate Competence Center Embedded Linux
>
[-- Attachment #1.2: Type: text/html, Size: 3732 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: gpg: can't connect to the agent: IPC connect call failed
2019-10-01 16:55 ` vijai kumar
@ 2019-10-01 17:22 ` Jan Kiszka
2019-10-01 17:41 ` Vijai Kumar K
0 siblings, 1 reply; 8+ messages in thread
From: Jan Kiszka @ 2019-10-01 17:22 UTC (permalink / raw)
To: vijai kumar, isar-users
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
>
> - 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
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: gpg: can't connect to the agent: IPC connect call failed
2019-10-01 17:22 ` Jan Kiszka
@ 2019-10-01 17:41 ` Vijai Kumar K
0 siblings, 0 replies; 8+ messages in thread
From: Vijai Kumar K @ 2019-10-01 17:41 UTC (permalink / raw)
To: Jan Kiszka; +Cc: vijai kumar, isar-users
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
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: gpg: can't connect to the agent: IPC connect call failed
2019-10-01 16:00 ` Jan Kiszka
@ 2019-10-01 18:27 ` Baurzhan Ismagulov
0 siblings, 0 replies; 8+ messages in thread
From: Baurzhan Ismagulov @ 2019-10-01 18:27 UTC (permalink / raw)
To: isar-users
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.
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2019-10-01 18:27 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-10-01 15:45 gpg: can't connect to the agent: IPC connect call failed 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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox