From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver Subject: bug#36855: guix system switch-generation doesn't Date: Wed, 28 Aug 2019 14:46:56 -0400 Message-ID: <875zmhm8jo.fsf__37193.002241996$1567018305$gmane$org@netris.org> References: <7BE8190F-A8E9-454E-8F37-FBFE42FBDE10@vllmrt.net> <87zhkkojfv.fsf@dustycloud.org> <877e7on3zd.fsf@sdf.lonestar.org> <87h86ry5j5.fsf@gmail.com> <874l241bq6.fsf__35802.4716888153$1566814098$gmane$org@gnu.org> <87woezoj3p.fsf__10757.9769611888$1566845612$gmane$org@netris.org> <87tva2m8ki.fsf@netris.org> <87y2zdnnrl.fsf__16000.9061962896$1567017269$gmane$org@sdf.lonestar.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:34635) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1i32zH-0000xX-4a for bug-guix@gnu.org; Wed, 28 Aug 2019 14:48:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1i32zD-0007OH-Ff for bug-guix@gnu.org; Wed, 28 Aug 2019 14:48:06 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:42387) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1i32zC-0007Ng-MB for bug-guix@gnu.org; Wed, 28 Aug 2019 14:48:03 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1i32zC-0004wP-JG for bug-guix@gnu.org; Wed, 28 Aug 2019 14:48:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: 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") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: "Jakob L. Kreuze" Cc: guix-devel@gnu.org, 36855@debbugs.gnu.org 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