From: Emmanuel Medernach <Emmanuel.Medernach@iphc.cnrs.fr>
To: Julien Lepiller <julien@lepiller.eu>, help-guix@gnu.org
Subject: Re: Trying to replicate guix packages list on another machine
Date: Mon, 27 Jun 2022 16:56:15 +0200 [thread overview]
Message-ID: <4e068700-c40d-b5e7-b629-d1decadef351@iphc.cnrs.fr> (raw)
In-Reply-To: <C4CC8D62-08CF-45D3-939C-C9F61560B757@lepiller.eu>
Le 27/06/2022 à 16:42, Julien Lepiller a écrit :
> It's possible your packages on machine A are from various guix
> revisions, if you didn't run "guix update" or didn't use a manifest to
> install them.
>
Yes you are right, that is certainly the case
> Eg you run "guix install glibc" at revision A, pull revision B where
> glibc was updated to 2.34. When you list your packages, it still
> mentions glibc@2.33 because you didn't update it. Then you try to
> replicate it on another machine by pulling revision B, but that old
> glibc is no longer available.
>
> Manifests ensure that all packages are from the same revision,
> although if you pull a new guix without reinstalling the manifest,
> you'll have the same issue because you're confusing the guix version
> from which the package was installed, and the current guix version.
>
Then how to install this previous glibc with other packages on machine B ?
Emmanuel
> On June 27, 2022 3:49:58 PM GMT+02:00, Emmanuel Medernach
> <Emmanuel.Medernach@iphc.cnrs.fr> wrote:
>
> Hello,
>
> We are trying to replicate guix packages list on another machine. We are using GUIX on a foreign distro.
>
> Here what we have on machine A:
>
> [Machine A]$ guix describe --format=channels
> (list (channel
> (name 'guix)
> (url"https://git.savannah.gnu.org/git/guix.git")
> (commit
> "a0178d34f582b50e9bdbb0403943129ae5b560ff")
> (introduction
> (make-channel-introduction
> "9edb3f66fd807b096b48283debdcddccfea34bad"
> (openpgp-fingerprint
> "BBB0 2DDF 2CEA F6A8 0D1D E643 A2A0 6DF2 A33A 54FA")))))
>
> [Machine A]$ guix package --list-installed | sort | awk '//{ print $1 "@" $2; }'
> cmake@3.19.2
> gcc-toolchain@4.9.4
> glibc@2.33
> gsl@2.6
> icu4c@68.2
> make@4.3
> pcre@8.44
> zlib@1.2.11
>
> But on machine B:
>
> [Machine B]$ cat ~/.config/guix/channels.scm
> (list (channel
> (name 'guix)
> (url"https://git.savannah.gnu.org/git/guix.git")
> (commit
> "a0178d34f582b50e9bdbb0403943129ae5b560ff")
> (introduction
> (make-channel-introduction
> "9edb3f66fd807b096b48283debdcddccfea34bad"
> (openpgp-fingerprint
> "BBB0 2DDF 2CEA F6A8 0D1D E643 A2A0 6DF2 A33A 54FA")))))
>
> [Machine B]$ guix installcmake@3.19.2 gcc-toolchain@4.9.4 glibc@2.33 gsl@2.6 icu4c@68.2 make@4.3 pcre@8.44 zlib@1.2.11
> guix install: error: glibc: package not found for version 2.33
>
> What are we doing wrong ? Please tell us what steps are missing to correctly replicate guix packages to another machine ?
>
> Best regards,
>
> Emmanuel Medernach
>
>
>
prev parent reply other threads:[~2022-06-27 14:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 13:49 Trying to replicate guix packages list on another machine Emmanuel Medernach
2022-06-27 14:32 ` zimoun
2022-06-27 14:51 ` Emmanuel Medernach
2022-06-27 15:39 ` zimoun
2022-06-28 6:30 ` Emmanuel Medernach
2022-06-28 8:08 ` zimoun
2022-06-27 14:42 ` Julien Lepiller
2022-06-27 14:56 ` Emmanuel Medernach [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
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=4e068700-c40d-b5e7-b629-d1decadef351@iphc.cnrs.fr \
--to=emmanuel.medernach@iphc.cnrs.fr \
--cc=help-guix@gnu.org \
--cc=julien@lepiller.eu \
/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).