Re: Problem with guix copy

[Emmanuel Medernach <Emmanuel.Medernach@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