From: "Ludovic Courtès" <ludo@gnu.org>
To: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
Cc: 40612@debbugs.gnu.org
Subject: bug#40612: guix build system --dry-run is broken
Date: Wed, 15 Apr 2020 18:56:04 +0200 [thread overview]
Message-ID: <87d088sn6j.fsf@gnu.org> (raw)
In-Reply-To: <20200414171632.41dae6fd@alma-ubu> ("Björn Höfling"'s message of "Tue, 14 Apr 2020 17:16:32 +0200")
Hello!
Björn Höfling <bjoern.hoefling@bjoernhoefling.de> skribis:
> On Mon, 13 Apr 2020 17:31:56 -0400
> Mark H Weaver <mhw@netris.org> wrote:
>
>> I guess this is related to the recent changes in graft handling, where
>> --dry-run (a.k.a. -n) no longer implies --no-grafts. It's not working
>> well for me. I hadn't updated my system since before those grafting
>> changes were made, and there's a lot for me to rebuild (I don't use
>> substitutes). I was very surprised to see this small output:
>
> Hi Mark,
>
> I can confirm this behavior for "guix system". I'm on
Yeah, it has to do with the new build handler and the lack of
“parallelism” when building the system derivation:
https://lists.gnu.org/archive/html/guix-devel/2020-03/msg00337.html
I think we’ll improve it over time by introducing more parallelism
there.
Fundamentally though, we have to understand that ‘--dry-run’ can only
print the first derivation plans, not those that are dynamically built
as a function of build results.
Thanks,
Ludo’.
next prev parent reply other threads:[~2020-04-15 16:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-13 21:31 bug#40612: guix build system --dry-run is broken Mark H Weaver
2020-04-14 15:16 ` Björn Höfling
2020-04-15 16:56 ` Ludovic Courtès [this message]
2020-04-17 19:50 ` Mark H Weaver
2020-04-18 16:53 ` Ludovic Courtès
2020-04-19 21:50 ` Mark H Weaver
2020-04-21 14:48 ` Ludovic Courtès
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=87d088sn6j.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=40612@debbugs.gnu.org \
--cc=bjoern.hoefling@bjoernhoefling.de \
/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.