Bug#972525: fixed in gnupg2 2.2.27-1
Aurelien Jarno wrote: > control: reopen 972525 > control: found 972525 gnupg2/2.2.27-2 Thanks a lot for sharing the fact. I assume that the failure occurs in a situation of heavy load, where it takes time for gpg-agent to start its service. In upstream, I opened another ticket, because I found a possible cause of this issue (another one): https://dev.gnupg.org/T5884 The change of GnuPG 2.3 in master: https://dev.gnupg.org/rGd94b411f129f572aace005f38cd78515d810135a can be applied manually. (Manually, because we had spell fix of the comment in 2.3.) --
Bug#972525: fixed in gnupg2 2.2.27-1
control: reopen 972525 control: found 972525 gnupg2/2.2.27-2 On 2021-02-08 23:18, Debian FTP Masters wrote: >* debian/patches/gpg-change-agent-spawn-2019-07-24-v2.patch: New patch to > fix a race condition, backported from master (Closes: #868550, #972525). Although it *seems* to happen less often, we still observe the failure from time to time on the buildds. For instance: Signature with key '37B76E354F4D3F4EB64D699B374AD85D2226CD3D' requested: signfile buildinfo /home/buildd/build/linux_5.10.92-2_amd64-buildd.buildinfo 37B76E354F4D3F4EB64D699B374AD85D2226CD3D gpg: can't connect to the agent: IPC connect call failed gpg: keydb_search failed: No agent running gpg: skipped "37B76E354F4D3F4EB64D699B374AD85D2226CD3D": No agent running gpg: /tmp/debsign.12nNJjLy/linux_5.10.92-2_amd64-buildd.buildinfo: clear-sign failed: No agent running debsign: gpg error occurred! Aborting signature.asc Description: PGP signature
