all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Mike Gerwitz <mtg@gnu.org>
Cc: help-guix@gnu.org
Subject: Re: "guix-latest" differs when two users run "guix pull" from same commit
Date: Mon, 08 Jan 2018 16:37:54 +0100	[thread overview]
Message-ID: <877esse4z1.fsf@gnu.org> (raw)
In-Reply-To: <87lghae7kd.fsf@gnu.org> (Mike Gerwitz's message of "Sat, 06 Jan 2018 21:17:22 -0500")

Mike Gerwitz <mtg@gnu.org> skribis:

> On Thu, Dec 07, 2017 at 22:57:17 -0800, Chris Marusich wrote:
>> Chris Marusich <cmmarusich@gmail.com> writes:
>>
>>> ludo@gnu.org (Ludovic Courtès) writes:
>>>
>>>> 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!  :-)
>>>
>>> I see!  Nice to know my suspicions were correct.
>>
>> Ludo, did you fix this recently?  Anecdotally, I noticed that the
>> problem no longer occurs using a recent version of Guix.
>
> I still seem to have this issue.
>
> My workaround is to just manually symlink ~/.config/guix/latest to the
> same derivation as root's.  Since Ludo said this behavior seems to be a
> bug, can I assume that it is safe to do so?

Yes, it’s a safe workaround.

I do hope to finish and merge ‘wip-pull-reload’ ASAP, which fixes this
among other things…

Ludo’.

      reply	other threads:[~2018-01-08 15:38 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
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 [this message]

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=877esse4z1.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=help-guix@gnu.org \
    --cc=mtg@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.