From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: 28310@debbugs.gnu.org
Subject: bug#28310: guix build -n misses package builds
Date: Sat, 02 Sep 2017 01:08:12 +0200 [thread overview]
Message-ID: <87a82exbj7.fsf@gnu.org> (raw)
In-Reply-To: <20170831190334.GA6673@jurong> (Andreas Enge's message of "Thu, 31 Aug 2017 21:03:34 +0200")
Hello,
Andreas Enge <andreas@enge.fr> skribis:
> I am right now in the process of updating pari-gp to version 2.9.3.
> After building it on a git check-out of three days ago, which went smoothly,
> I rebased my patch on today's master and was pleased to see that no rebuild
> was needed:
>
> $ ./pre-inst-env guix build pari-gp -n
> outputs nothing.
>
> However, once the -n dropped, the gd package gets built.
> And then it is starting ruby, which has no connection to pari-gp:
> Downloading https://mirror.hydra.gnu.org/guix/nar/229n3pzp5bdmbdvwslg0dxliysas92k5-ruby-2.4.1.tar.xz...
> ruby-2.4.1.tar.xz 9.5MiB 22KiB/s 00:06 [ ] 1.3%^
“-n” now implies “--no-grafts” (commit
fd59105c49965db956fac73c68d8b00d068f5d5c). This was motivated by the
need to have -n really perform a dry run.
The downside is that with -n we now see only half of the build plan, and
when we remove -n, we start with the other half of the build plan,
grafting.
The “build continuation” idea of ‘wip-gexp-grafts’, discussed in
<https://bugs.gnu.org/22990>, could in theory help with that.
Ludo’.
next prev parent reply other threads:[~2017-09-01 23:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-31 19:03 bug#28310: guix build -n misses package builds Andreas Enge
2017-09-01 23:08 ` Ludovic Courtès [this message]
2017-09-02 10:04 ` Andreas Enge
2017-09-02 20:13 ` Ludovic Courtès
2017-09-07 12:42 ` Andreas Enge
2017-09-07 13:24 ` Ludovic Courtès
2020-03-22 11: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
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=87a82exbj7.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=28310@debbugs.gnu.org \
--cc=andreas@enge.fr \
/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).