From: Andreas Schwab <schwab@linux-m68k.org>
To: Christian Couder <christian.couder@gmail.com>
Cc: NSENGIYUMVA WILBERFORCE <nsengiyumvawilberforce@gmail.com>,
git@vger.kernel.org
Subject: Re: Github actions failing
Date: Mon, 09 Jan 2023 11:10:45 +0100 [thread overview]
Message-ID: <87pmbo2f2y.fsf@igel.home> (raw)
In-Reply-To: <CAP8UFD23ObbQaeQi2WsZ3oy0QTKiBxs3wExaHTU2QzJBPwKOmA@mail.gmail.com> (Christian Couder's message of "Mon, 9 Jan 2023 10:22:01 +0100")
On Jan 09 2023, Christian Couder wrote:
>> > 1870 + test 2 -ne 2
>> > 1871 + eval diff -u "$@"
>> > 1872 + diff -u actual expected
>> > 1873 --- actual 2023-01-08 19:40:42.169214115 +0000
>> > 1874 +++ expected 2023-01-08 19:40:42.121213837 +0000
>> > 1875 @@ -1,4 +1,5 @@
>> > 1876 gpg: Signature made Sun Jan 8 19:40:42 2023 UTC
>> > 1877 gpg: using DSA key 13B6F51ECDDE430D
>> > 1878 +gpg: checking the trustdb
>
> The + before "gpg" means that the above line is in what we expect, but
> not in what we actually get.
>
> I think the reason might be that gpg's output could have changed
> between different versions of gpg and it might just not be possible
> and wise to rely on the exact output it emits.
I think the "checking the trustdb" message is time-dependent, as the
trustdb is normally updated only after some interval has passed.
According to the gpg manpage, automatic trustdb checking can be
suppressed with --no-auto-check-trustdb.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2023-01-09 10:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-08 10:02 Github actions failing NSENGIYUMVA WILBERFORCE
2023-01-08 10:07 ` NSENGIYUMVA WILBERFORCE
2023-01-08 18:17 ` Christian Couder
2023-01-09 4:40 ` NSENGIYUMVA WILBERFORCE
2023-01-09 9:22 ` Christian Couder
2023-01-09 10:10 ` Andreas Schwab [this message]
2023-01-09 13:01 ` NSENGIYUMVA WILBERFORCE
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pmbo2f2y.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=nsengiyumvawilberforce@gmail.com \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.