Bug#972525: buildd: sbuild randomly fails to sign changes file despite valid signature keys
Source: sbuild
Version: 0.80.0
Severity: normal
User: debian-sparc@lists.debian.org
Usertags: sparc64
Hi!
I'm observing random failures of sbuild signing the changes file after build
on some buildds, especially on sparc64 and most often on the machine sompek.
I'm not sure yet what the problem is but it looks like a GPG problem [1]:
gpg: can't connect to the agent: IPC connect call failed
gpg: keydb_search failed: No agent running
gpg: skipped "F1EA40F487003E5047A04D0A62D1430FE7E0DE86": No agent running
gpg: /tmp/debsign.oB0Milcr/rust-kstring_1.0.0-1_sparc64.changes: clear-sign failed: No agent running
debsign: gpg error occurred! Aborting....
I'm filing this issue here to get some attention and maybe some ideas where
the problem could be. Maybe sbuild should wait a little longer before attempting
to sign? Or maybe the GPG daemon is crashing often?
In case it's safe not to be an issue with buildd/sbuild, feel free to reassign.
Thanks,
Adrian
> [1] https://buildd.debian.org/status/fetch.php?pkg=rust-kstring&arch=sparc64&ver=1.0.0-1&stamp=1603142545&raw=0
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Reply to: