From: "Ludovic Courtès" <ludo@gnu.org>
To: Christopher Baines <mail@cbaines.net>
Cc: 44559@debbugs.gnu.org
Subject: bug#44559: gnutls 3.6.12 fails to build: FAIL: status-request-revoked
Date: Thu, 12 Nov 2020 22:06:09 +0100 [thread overview]
Message-ID: <87v9eaffpa.fsf@gnu.org> (raw)
In-Reply-To: <87d00los2d.fsf@cbaines.net> (Christopher Baines's message of "Tue, 10 Nov 2020 20:49:46 +0000")
Hi,
Christopher Baines <mail@cbaines.net> skribis:
> I found this when trying to build guile3.0-gnutls:
>
> guix time-machine --commit=94585fffb23079fe71110e2bf99782eb4ccfa12b -- build --no-grafts --check guile3.0-gnutls
>
>
> FAIL: status-request-revoked
> ============================
>
> trying NORMAL:-VERS-ALL:+VERS-TLS1.2
> received status request
> received status request
> cert_verify_callback:263: certificate verify status doesn't match: 100402 != 22FAIL status-request-revoked (exit status: 1)
This was fixed upstream between 3.6.12 and 3.6.14 with this patch by
Bernhard (it’s a small world!):
--8<---------------cut here---------------start------------->8---
commit ed208fe55f31478732fd6cc394f9576b315a42cd
Author: Bernhard M. Wiedemann <bwiedemann@suse.de>
Date: Sun Apr 5 15:09:57 2020 +0200
tests: Fix status-request-revoked after 2020-10-24
included certs expire 2020-10-24 so this test fails after that date.
Fixes #967
This patch was done while working on reproducible builds for openSUSE.
Signed-off-by: Bernhard M. Wiedemann <bwiedemann@suse.de>
--8<---------------cut here---------------end--------------->8---
The question for us becomes how to ensure long-term reproducibility in
the presence of such bugs.
In this case, I think the only solution would be to change the system
clock when one rebuilds GnuTLS (or to use ‘--without-tests=gnutls’, but
you end up with different derivations, which is not necessarily
desirable).
Thoughts?
Ludo’.
next prev parent reply other threads:[~2020-11-12 21:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 20:49 bug#44559: gnutls 3.6.12 fails to build: FAIL: status-request-revoked Christopher Baines
2020-11-12 21:06 ` Ludovic Courtès [this message]
2020-11-12 21:18 ` Marius Bakke
2020-11-15 11:05 ` Ludovic Courtès
2020-12-31 0:27 ` bug#44559: Solution jeremiah
2021-02-16 21:00 ` bug#44559: Carl Dong
2021-02-16 21:49 ` bug#44559: Leo Famulari
2021-02-19 15:33 ` bug#44559: Ludovic Courtès
2021-02-19 18:32 ` bug#44559: Maxime Devos
2021-02-20 13:46 ` bug#44559: Ludovic Courtès
2021-02-20 14:12 ` bug#44559: Detecting “expiring” builds Ludovic Courtès
2021-02-19 23:49 ` bug#44559: Carl Dong
2021-02-22 22:36 ` bug#44559: Christopher Baines
2021-02-23 8:41 ` bug#44559: Ludovic Courtès
2021-02-23 8:55 ` bug#44559: Christopher Baines
2022-07-13 15:03 ` bug#44559: gnutls 3.6.12 fails to build: FAIL: status-request-revoked Maxim Cournoyer
2022-07-15 13:17 ` Ludovic Courtès
2022-07-16 1:33 ` Maxim Cournoyer
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=87v9eaffpa.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=44559@debbugs.gnu.org \
--cc=mail@cbaines.net \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
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.