[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Guix installing different package versions on different machines

From: Tobias Geerinckx-Rice
Subject: Re: Guix installing different package versions on different machines
Date: Sat, 28 Sep 2019 16:41:56 +0200


Zelphir Kaltstahl 写道:
I installed Guix on my own machine (Xubuntu 18.04.3) and at work on my machine (Ubuntu 18.04.3). Although I do `guix pull` and then `guix package -u`, both machines get different versions of packages installed
this way.

Guile (home: 2.2.4, work: 2.2.6).

This is not normal. GNU Guile 2.2.6 was added to Guix almost 3 months ago.

What does ‘guix describe’ return on both machines? Something recent? You can look up the commit IDs in the git history.

What does ‘which guix’ say? It should print the same thing on both machines (/home/you!/.config/guix/current/bin/guix). Certainly not /usr/local/bin/guix or anything like that.

I don't
understand this behavior, as I thought that both installations of Guix should use the same repositories, because I installed them the same way and I even use the same OS at the core. Furthermore I thought, that Guix installs packages as they have been provided by contributors and does not perform checks, whether some package is suitable on a system.

Where is my understanding wrong?

Trick question :-)  Your understanding is, generally, correct.

What can lead to this behavior?

Guix doesn't strictly ‘use repositories’: package definitions are part of and updated in sync with the package manager, which is why it matters *which* guix runs when you invoke it and why I'm interested in the output of ‘which guix’ above. ‘guix pull’ *only* updates /home/you!/.config/guix/current/bin/guix.

Packages can be marked as unsupported on certain architectures (e.g. i686 vs. x86_64 or aarch64) and/or kernels (the Hurd or Linux), but guile@2.2.6 supports all of them.

AFAIK Guix only runs on one OS (GNU), so that can't affect things either.

Jesse Gibbons 写道:
To make sure all package versions match, write cron jobs to do this at the
same time on both machines.

Yes. If said matching is really important to you, having all machines ‘git pull --commit=…’ to the same commit is even better but requires some communication between them.

Kind regards,


Attachment: signature.asc
Description: PGP signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]