From: Emmanuel Medernach <Emmanuel.Medernach@iphc.cnrs.fr>
To: guix-science@gnu.org
Subject: Re: Problem with guix copy
Date: Fri, 15 Mar 2024 15:50:18 +0100 [thread overview]
Message-ID: <d348fe47-5c9a-4d81-85d3-c631133fbf3e@iphc.cnrs.fr> (raw)
In-Reply-To: <6803db02-00c9-4fbd-8cae-7b5985e2d1f6@iphc.cnrs.fr>
Le 15/03/2024 à 15:37, Emmanuel Medernach a écrit :
>
> Le 15/03/2024 à 15:10, Andreas Enge a écrit :
>> Hello,
>>
>> Am Fri, Mar 15, 2024 at 02:58:23PM +0100 schrieb Emmanuel Medernach:
>>> Now on both machines guix and guix-daemon used are the same, here
>>> are both
>>> paths:
>>> /gnu/store/m79ld7h62wjbx6kc2jip73lmh8lfc8qs-guix-command
>>> /gnu/store/z642sncd5jgj4bc3p18rdqwdkq30p833-guix-daemon
>>> When I try a guix copy the requested hash is still different from
>>> the one on
>>> Machine_A (and it wishes to recompile it):
>> just a wild guess, but could it be that you did a "guix gc" on Machine A
>> and that there are grafts in play? In that case the ungrafted package
>> may
>> have been deleted, and will then be recomputed.
>>
>> Maybe you could try the same operation adding --no-grafts to the
>> command.
>
> Thanks for your idea, here is the result:
>
> Machine_A # guix package --manifest="$HOME"/manifests/bazel.scm
> --no-grafts --no-substitutes
> Machine_A # guix package --list-installed | grep bazel
> bazel 6.4.0 out
> /gnu/store/8xmcsk5jrkxb06whgj0fif0mrxvhyvj6-bazel-6.4.0
>
> The hash has changed but is still not the one requested by Machine_B
> with guix copy (same message there)
>
> I cannot publish from Machine_A to Machine_B (but I don't know if that
> would be better or not)
>
Ok for the time being I give up and will compile bazel on Machine_B, but
I am curious why the hash requested from Machine_B is not the one built
on Machine_A ?
The problem is that I will have many machines like Machine_B and I would
like to avoid recompilation of packages on all of them if possible.
Emmanuel
next prev parent reply other threads:[~2024-03-15 14:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-15 9:14 Problem with guix copy Emmanuel Medernach
2024-03-15 9:21 ` Emmanuel Medernach
2024-03-15 13:58 ` Emmanuel Medernach
2024-03-15 14:10 ` Andreas Enge
2024-03-15 14:37 ` Emmanuel Medernach
2024-03-15 14:50 ` Emmanuel Medernach [this message]
2024-03-19 10:26 ` Simon Tournier
2024-03-19 15:40 ` Emmanuel Medernach
2024-03-19 15:51 ` Emmanuel Medernach
2024-03-21 22:19 ` Simon Tournier
2024-03-25 10:13 ` Emmanuel Medernach
2024-03-27 13:05 ` Simon Tournier
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=d348fe47-5c9a-4d81-85d3-c631133fbf3e@iphc.cnrs.fr \
--to=emmanuel.medernach@iphc.cnrs.fr \
--cc=guix-science@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.