From: "Ludovic Courtès" <ludo@gnu.org>
To: 55506-done@debbugs.gnu.org
Subject: bug#55506: ‘tests/channels.scm’ and ‘tests/git-authenticate.scm’ GPG-related test failures
Date: Thu, 19 May 2022 00:09:17 +0200 [thread overview]
Message-ID: <87a6be1oj6.fsf@gnu.org> (raw)
In-Reply-To: <87y1yy22lj.fsf@inria.fr> ("Ludovic Courtès"'s message of "Wed, 18 May 2022 19:05:28 +0200")
Ludovic Courtès <ludo@gnu.org> 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’.
prev parent reply other threads:[~2022-05-18 22:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 17:05 bug#55506: ‘tests/channels.scm’ and ‘tests/git-authenticate.scm’ GPG-related test failures Ludovic Courtès
2022-05-18 22:09 ` Ludovic Courtès [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a6be1oj6.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=55506-done@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).