From: ludo@gnu.org (Ludovic Courtès)
To: Chris Marusich <cmmarusich@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: "guix-latest" differs when two users run "guix pull" from same commit
Date: Thu, 16 Nov 2017 17:08:12 +0100 [thread overview]
Message-ID: <87o9o2cikz.fsf@gnu.org> (raw)
In-Reply-To: <87ineaewkt.fsf@gmail.com> (Chris Marusich's message of "Wed, 15 Nov 2017 14:58:07 -0800")
Chris Marusich <cmmarusich@gmail.com> skribis:
> When two users run "guix pull" using the same commit, two different
> versions of "guix-latest" get built. This surprised me, and in any case
> it seems inefficient to build the same version of Guix two times. Why
> do two different derivations get built?
That’s a bug! :-)
> Here's an invocation of "guix pull" as an unprivileged user:
>
> $ guix pull
> ...
> Building from Git commit ed0f9f53abef57b9f33d3b2eada40375894bdff6...
> ...
> The following derivation will be built:
> /gnu/store/m3x8069x5aspc29m9ay7idndz0kpfxlb-guix-latest.drv
> copying and compiling to '/gnu/store/dn13gs9w16h5w6l77pnpbclqxnbyhh4m-guix-latest' with Guile 2.2.2...
>
>
> And here's an invocation of "guix pull" as root:
>
> # guix pull
> ...
> Building from Git commit ed0f9f53abef57b9f33d3b2eada40375894bdff6...
> ...
> The following derivation will be built:
> /gnu/store/675pz9f4qz9dd4jikzcgzv62kjrxfhmg-guix-latest.drv
> copying and compiling to '/gnu/store/cvc0rf65s3mjw9rjps80ram3898qdws3-guix-latest' with Guile 2.2.2...
Can you compare the two ‘guix-latest’ outputs with ‘diff -r’? I’m
guessing the difference stems from (guix config).
Thanks,
Ludo’.
next prev parent reply other threads:[~2017-11-16 16:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-15 22:58 "guix-latest" differs when two users run "guix pull" from same commit Chris Marusich
2017-11-16 16:08 ` Ludovic Courtès [this message]
2017-11-22 3:53 ` Chris Marusich
2017-12-08 6:57 ` Chris Marusich
2017-12-08 10:44 ` Ludovic Courtès
2018-01-07 2:17 ` Mike Gerwitz
2018-01-08 15:37 ` 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=87o9o2cikz.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=cmmarusich@gmail.com \
--cc=help-guix@gnu.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 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.