Ludovic Courtès <[email protected]> skribis: > Notice “error: gpg failed to sign the data”, which comes from Git. > > When stracing, we see this: > > 13587 write(2, "[GNUPG:] KEY_CONSIDERED > 44D31E21AF7138F9B632280A771F49CBFAAE072D 3", 66) = 66 > 13581 <... poll resumed>) = 1 ([{fd=7, revents=POLLIN}]) > 13587 write(2, "\n", 1 <unfinished ...> > 13581 read(7, <unfinished ...> > 13587 <... write resumed>) = 1 > 13581 <... read resumed>"[GNUPG:] KEY_CONSIDERED > 44D31E21AF7138F9B632280A771F49CBFAAE072D 3\n", 8192) = 67 > 13581 poll([{fd=5, events=POLLIN}, {fd=7, events=POLLIN}], 2, -1 <unfinished > ...> > 13587 read(3, "", 8192) = 0 > 13587 brk(0x13bf000) = 0x13bf000 > 13587 write(2, "gpg: skipped \"44D3 1E21 AF71 38F9 B632 280A 771F 49CB FAAE > 072D\": Unusable secret key", 86) = 86
Turns out those keys all had an expiration date (I guess that’s what gpg does by default), and one of them expired a few weeks ago. I removed the expiration date with ‘gpg --edit-key’ and exported the resulting public keys (“OpenPGP certificates”) as tests/keys/*.pub. Fixed in 3ae7632ca0a1edca9d8c3c766efb0dcc8aa5da37. Ludo’.
