From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 44559-done@debbugs.gnu.org, Mathieu Othacehe <othacehe@gnu.org>,
Christopher Baines <mail@cbaines.net>,
Carl Dong <contact@carldong.me>
Subject: bug#44559: gnutls 3.6.12 fails to build: FAIL: status-request-revoked
Date: Fri, 15 Jul 2022 21:33:46 -0400 [thread overview]
Message-ID: <87y1wtsux1.fsf@gmail.com> (raw)
In-Reply-To: <87wnce7bwr.fsf@gnu.org> ("Ludovic Courtès"'s message of "Fri, 15 Jul 2022 15:17:40 +0200")
Hi,
Ludovic Courtès <ludo@gnu.org> writes:
> Hi,
>
> Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:
>
>> I lost track of the details -- is this problem still likely to bite us
>> in the future, or was something committed to mitigate against it?
>
> “Time bombs” are the worst of non-reproducibility bugs because (1) we
> don’t have workarounds other than changing the system time on the
> machine that performs the build, and (2) we currently lack a way to
> detect them.
I see. Thanks for explaining!
> In this thread, Chris and I proposed addressing #2 by offering ways to
> automatically or manually run builds “in the future”¹. We could actually
> similarly address #1 by running builds “in the past”.
>
> In any case, the first step is probably to offer a VM service for Guix
> System, similar to childhurd, with an option to specify the starting
> time.
>
> So we’re not done yet, but the discussion has drifted beyond the
> original GnuTLS bug report, so perhaps we can close it and take it
> elsewhere?
I think so! Few seems to visit these years old reports. If there's
something to brainstorm about, I'd rather see it happen in a new thread
on guix-devel.
Thanks for the reply!
Closing.
Maxim
prev parent reply other threads:[~2022-07-16 1:34 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
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 [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y1wtsux1.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=44559-done@debbugs.gnu.org \
--cc=contact@carldong.me \
--cc=ludo@gnu.org \
--cc=mail@cbaines.net \
--cc=othacehe@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 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.