From: Emmanuel Medernach <Emmanuel.Medernach@iphc.cnrs.fr>
To: guix-science@gnu.org
Subject: Re: Problem with guix copy
Date: Fri, 15 Mar 2024 10:21:27 +0100 [thread overview]
Message-ID: <8fd0feda-7b79-40e2-8efd-39397e73ed38@iphc.cnrs.fr> (raw)
In-Reply-To: <daa00538-cd40-4ea6-9b40-3725fd66fd47@iphc.cnrs.fr>
Le 15/03/2024 à 10:14, Emmanuel Medernach a écrit :
> Hello,
>
> I have problems with guix copy: I have 2 machines Machine_A and
> Machine_B. They both have the same channels. Machine_B is slow (I
> don't want to recompile there, I would like to reuse the same packages
> from Machine_A). Machine_A and Machine_B have limited connectivity,
> Machine_A has only ssh access (I cannot use it as a substitute with
> guix publish) and Machine_B has nothing.
>
> I installed bazel on Machine_A:
>
>
If that could help, here is a minimal manifest and command I use to
install it in an extra profile:
(specifications->manifest
'("glibc-locales"
"bazel"
))
# guix package --manifest="$HOME"/manifests/bazel.scm
--profile="$GUIX_EXTRA_PROFILES"/bazel/profile
> Machine_A # guix build bazel
> /gnu/store/5i872l0ijm7vd9vk2knn67ai3daa6q68-bazel-6.4.0
> Machine_A # readlink -f $GUIX_EXTRA_PROFILES/bazel/profile/bin/bazel
> /gnu/store/5i872l0ijm7vd9vk2knn67ai3daa6q68-bazel-6.4.0/bin/bazel
>
> I tried guix copy, but I have 2 problems:
>
> First, Machine_B asks for a different hash that the one I have on
> Machine_A (even if both have the same channels):
>
> Machine_B # guix copy --from=Machine_A --dry-run bazel
> guix copy: error: no such item on remote host 'Machine_A':
> /gnu/store/6n69a11yjydwhb7p8kb6qg20nj5cxrg1-bazel-6.4.0
>
> Second, when I try to copy the package with the hash from Machine_A I
> get an error:
>
> Machine_B # guix copy --from=Machine_A --dry-run
> /gnu/store/5i872l0ijm7vd9vk2knn67ai3daa6q68-bazel-6.4.0
> retrieving 1 store item from 'Machine_A'...
> guix copy: error: implementation cannot deal with > 32-bit integers
>
> How to use guix copy to transfer the same packages from one machine to
> another ?
>
> Here are my current channels:
>
> (list (channel
> (name 'guix-science)
> (url "https://github.com/guix-science/guix-science.git")
> (branch "master")
> (commit
> "61836bfd9c3a01b696142aabb625b0851d6fd536")
> (introduction
> (make-channel-introduction
> "b1fe5aaff3ab48e798a4cce02f0212bc91f423dc"
> (openpgp-fingerprint
> "CA4F 8CF4 37D7 478F DA05 5FD4 4213 7701 1A37 8446"))))
> (channel
> (name 'guix)
> (url "https://git.savannah.gnu.org/git/guix.git")
> (branch "master")
> (commit
> "7319b4d5286d31a9c6a889e81af72308efdaab41")
> (introduction
> (make-channel-introduction
> "9edb3f66fd807b096b48283debdcddccfea34bad"
> (openpgp-fingerprint
> "BBB0 2DDF 2CEA F6A8 0D1D E643 A2A0 6DF2 A33A 54FA")))))
>
> Thanks for your help
>
> Best regards,
>
> Emmanuel Medernach
>
next prev parent reply other threads:[~2024-03-15 12:25 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 [this message]
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
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
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=8fd0feda-7b79-40e2-8efd-39397e73ed38@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.
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).