From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 44559@debbugs.gnu.org, Mathieu Othacehe <othacehe@gnu.org>,
Carl Dong <contact@carldong.me>
Subject: bug#44559: Detecting “expiring” builds
Date: Sat, 20 Feb 2021 15:12:03 +0100 [thread overview]
Message-ID: <8735xqj0b0.fsf_-_@gnu.org> (raw)
In-Reply-To: <87v9amj1hn.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sat, 20 Feb 2021 14:46:28 +0100")
It occurred to me that, just like we have childhurds, we could provide a
service that sets up a sub-Guix System running in a VM with its clock
set years ahead, and you would offload to that. That’s not perfect, but
it’s a rather easy addition.
Another option would be to have built-in support in the daemon. If you
turn on some option, it would transparently run derivation builds in
qemu-user (does that support changing the system date?) or similar, but
that’s more work.
Ludo’.
next prev parent reply other threads:[~2021-02-20 14:13 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 ` Ludovic Courtès [this message]
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
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=8735xqj0b0.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=44559@debbugs.gnu.org \
--cc=contact@carldong.me \
--cc=maximedevos@telenet.be \
--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 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).