gpg: can't connect to the agent: IPC connect call failed
11 views
Skip to first unread message
Baurzhan Ismagulov
Oct 1, 2019, 11:45:55 AM10/1/19
to isar-...@googlegroups.com
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.
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.
Jan Kiszka
Oct 1, 2019, 12:00:22 PM10/1/19
to isar-...@googlegroups.com
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
> 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?
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
vijai kumar
Oct 1, 2019, 12:14:54 PM10/1/19
to isar-users
Hello Baurzhan,
Which fixes are we talking about here?
Thanks,
Vijai Kumar K
Jan Kiszka
Oct 1, 2019, 12:43:32 PM10/1/19
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
> Hello Baurzhan,
>
> Which fixes are we talking about here?
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+...@googlegroups.com
> <mailto:isar-users+...@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>.
vijai kumar
Oct 1, 2019, 12:55:23 PM10/1/19
to isar-users
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
> <mailto:isar-users+unsub...@googlegroups.com>.
Jan Kiszka
Oct 1, 2019, 1:22:05 PM10/1/19
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.
> 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.
Jan
> > <mailto:isar-users+...@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
> <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
>
>
> --
> 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+...@googlegroups.com
> 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
> <mailto:isar-users+...@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>.
Vijai Kumar K
Oct 1, 2019, 1:41:12 PM10/1/19
to Jan Kiszka, 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.
> 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
Thanks,
Vijai Kumar K
Baurzhan Ismagulov
Oct 1, 2019, 2:27:25 PM10/1/19
to isar-...@googlegroups.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
> 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)?
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.
Reply all
Reply to author
Forward
0 new messages