From: Mike Gerwitz <mtg@gnu.org>
To: Leo Famulari <leo@famulari.name>
Cc: 29449@debbugs.gnu.org
Subject: [bug#29449] [PATCH] gnu: node: Update to 8.9.1.
Date: Sun, 26 Nov 2017 23:54:26 -0500 [thread overview]
Message-ID: <87wp2cb9tp.fsf@gnu.org> (raw)
In-Reply-To: <20171126192405.GA1313@jasmine.lan> (Leo Famulari's message of "Sun, 26 Nov 2017 14:24:05 -0500")
[-- Attachment #1: Type: text/plain, Size: 931 bytes --]
On Sun, Nov 26, 2017 at 14:24:05 -0500, Leo Famulari wrote:
> --check and --rounds are a bit confusing when the package in question is
> grafted.
>
> Basically, grafting is treated as its own derivation, so doing
> `./pre-inst-env guix build --check node` just re-does the grafting
> derivation, instead of rebuilding node.
>
> Currently every package is grafted because we used a graft to fix a bug
> in glibc.
>
> So, try `./pre-inst-env guix build --no-grafts --check node`.
Ah, that makes sense, thank you for the clarification. I did start
--no-grafts, but that applied to dependencies as well it seemed, so I
stopped it. I'll let that run tonight (node takes a while to build on
the X200) and report back / provide an updated patch tomorrow.
--
Mike Gerwitz
Free Software Hacker+Activist | GNU Maintainer & Volunteer
GPG: D6E9 B930 028A 6C38 F43B 2388 FEF6 3574 5E6F 6D05
https://mikegerwitz.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2017-11-27 5:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-26 1:45 [bug#29449] [PATCH] gnu: node: Update to 8.9.1 Mike Gerwitz
2017-11-26 17:41 ` Ludovic Courtès
2017-11-26 19:10 ` Mike Gerwitz
2017-11-26 19:24 ` Leo Famulari
2017-11-27 4:54 ` Mike Gerwitz [this message]
2017-11-26 21:55 ` Jelle Licht
2017-11-27 4:57 ` Mike Gerwitz
2017-11-27 8:44 ` Ludovic Courtès
2017-11-28 2:29 ` Mike Gerwitz
2017-11-28 9:05 ` bug#29449: " Ludovic Courtès
2017-11-28 18:28 ` [bug#29449] " Leo Famulari
2017-11-28 22:46 ` 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=87wp2cb9tp.fsf@gnu.org \
--to=mtg@gnu.org \
--cc=29449@debbugs.gnu.org \
--cc=leo@famulari.name \
/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).