From: Mark H Weaver <mhw@netris.org>
To: "Jakob L. Kreuze" <zerodaysfordays@sdf.lonestar.org>
Cc: guix-devel@gnu.org, 36855@debbugs.gnu.org
Subject: Re: bug#36855: guix system switch-generation doesn't
Date: Wed, 28 Aug 2019 14:46:56 -0400 [thread overview]
Message-ID: <875zmhm8jo.fsf@netris.org> (raw)
In-Reply-To: <87y2zdnnrl.fsf__16000.9061962896$1567017269$gmane$org@sdf.lonestar.org> (Jakob L. Kreuze's message of "Wed, 28 Aug 2019 14:33:18 -0400")
Hi Jakob,
zerodaysfordays@sdf.lonestar.org (Jakob L. Kreuze) writes:
> Thanks for the input; I wasn't aware that the activation process was
> taking so long for some people. One of Ludovic's suggestions was to
> create a single derivation, rather than three, to speed up system
> activation. I'll look into this further.
To be clear, I don't care how long it takes to build these derivations.
However, I think they should all be built before starting to activate
the system. Does that make sense?
On a side note, what would happen if one of those builds failed? Would
the system activation be left half-done?
Thanks,
Mark
next prev parent reply other threads:[~2019-08-28 18:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7BE8190F-A8E9-454E-8F37-FBFE42FBDE10@vllmrt.net>
2019-08-06 21:25 ` guix system switch-generation doesn't Robert Vollmert
2019-08-07 19:37 ` bug#36855: " Christopher Lemmer Webber
2019-08-07 19:57 ` Jakob L. Kreuze
2019-08-08 16:40 ` Chris Marusich
2019-08-08 17:03 ` Robert Vollmert
2019-08-09 7:35 ` Chris Marusich
2019-08-26 10:07 ` Ludovic Courtès
2019-08-28 18:28 ` Jakob L. Kreuze
[not found] ` <874l241bq6.fsf__35802.4716888153$1566814098$gmane$org@gnu.org>
2019-08-26 18:51 ` Mark H Weaver
[not found] ` <87woezoj3p.fsf__10757.9769611888$1566845612$gmane$org@netris.org>
2019-08-28 0:34 ` Mark H Weaver
2019-08-28 18:33 ` Jakob L. Kreuze
[not found] ` <87y2zdnnrl.fsf__16000.9061962896$1567017269$gmane$org@sdf.lonestar.org>
2019-08-28 18:46 ` Mark H Weaver [this message]
2019-08-29 0:08 ` Jakob L. Kreuze
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=875zmhm8jo.fsf@netris.org \
--to=mhw@netris.org \
--cc=36855@debbugs.gnu.org \
--cc=guix-devel@gnu.org \
--cc=zerodaysfordays@sdf.lonestar.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).