From: Mark H Weaver <mhw@netris.org>
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: guix-devel@gnu.org
Subject: Re: updating list of substitutes
Date: Wed, 22 Apr 2015 15:01:37 -0400 [thread overview]
Message-ID: <87618o6l7y.fsf@netris.org> (raw)
In-Reply-To: <20150421163852.GA20008@thebird.nl> (Pjotr Prins's message of "Tue, 21 Apr 2015 18:38:52 +0200")
Pjotr Prins <pjotr.public12@thebird.nl> writes:
> On Tue, Apr 21, 2015 at 02:02:37PM +0200, Andreas Enge wrote:
>> On Tue, Apr 21, 2015 at 12:02:16PM +0200, Pjotr Prins wrote:
>> > ls /var/guix/profiles/per-user/wrk/guix-profile-2-link/bin/ruby
>> > /var/guix/profiles/per-user/wrk/guix-profile-2-link/bin/ruby -> /gnu/store/gy1dnlh6qhwd40admi3b1mr4r9cn8bww-ruby-2.2.1/bin/ruby
>> >
>> > A few days later I install ruby-1.8.7 followed by
>> > guix package -i ruby-2.2.1
>> > The following package will be upgraded:
>> > ruby 1.8.7-p374 -> 2.2.1 /gnu/store/z8kf6hgln4a7xf68pdnlibl3vcg5rl15-ruby-2.2.1
>>
>> But I suppose that in between, you also did a "git pull; make install" or
>> "guix pull"? Then it is clear that if you have a different version of guix
>> installed, it references different packages.
>
> I don't think so, but I am not 100% sure I did not do a guix pull in
> between. I'll show it if it happens again.
The different hash indicates that you had done a "guix pull" in between,
or else changed some package that 'ruby' depends on.
To reproduce the exact versions of packages that you had before, then
you need to be using the same version of 'guix' that you used before.
"guix pull" supports only one mode of operation: get the latest version
from the git repo and build it. It puts that latest version into
$HOME/.config/guix/latest. You may backup and restore that directory if
you wish.
If you want more flexibility (as I do), you will avoid "guix pull"
entirely and instead build and use guix from a git checkout using
'pre-inst-env'. Then you can add your own tags, or simply record the
git commit hashes, and then reproduce them at any time by checking out
the desired version of guix and using that one.
Using 'git' also allows you to keep a private branch with your own
arbitrary modifications, and to periodically either merge from our
upstream, cherry-pick from us, or rebase your branch onto our upstream,
whatever you prefer.
Mark
next prev parent reply other threads:[~2015-04-22 19:01 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-21 6:45 updating list of substitutes Pjotr Prins
2015-04-21 8:22 ` Ludovic Courtès
2015-04-21 8:40 ` Pjotr Prins
2015-04-21 9:19 ` Andreas Enge
2015-04-21 10:02 ` Pjotr Prins
2015-04-21 12:02 ` Andreas Enge
2015-04-21 16:38 ` Pjotr Prins
2015-04-22 19:01 ` Mark H Weaver [this message]
2015-04-22 11:46 ` Pjotr Prins
2015-04-22 12:24 ` Andreas Enge
2015-04-22 12:35 ` Pjotr Prins
2015-04-22 13:08 ` Taylan Ulrich Bayırlı/Kammer
2015-04-23 9:52 ` Ludovic Courtès
2015-05-26 12:42 ` Pjotr Prins
2015-05-26 20:50 ` Ludovic Courtès
2015-10-11 7:46 ` Pjotr Prins
2015-10-11 8:47 ` Efraim Flashner
2015-10-11 18:39 ` Ludovic Courtès
2015-10-11 21:27 ` Pjotr Prins
2015-10-12 5:15 ` Mark H Weaver
2015-10-12 6:06 ` Pjotr Prins
2015-10-12 16:31 ` Mark H Weaver
2015-10-12 21:12 ` Pjotr Prins
2015-10-12 17:03 ` Ludovic Courtès
2015-10-13 12:11 ` Pjotr Prins
2015-10-13 12:52 ` Andreas Enge
2015-10-13 14:35 ` Ludovic Courtès
2015-11-18 16:15 ` Pjotr Prins
2015-11-18 16:28 ` Thompson, David
2015-11-18 16:30 ` Alex Sassmannshausen
2015-11-18 18:29 ` Funding the build farm Ludovic Courtès
2015-11-18 18:38 ` Cook, Malcolm
2015-11-18 20:55 ` Pjotr Prins
2015-11-18 21:20 ` Ludovic Courtès
2015-11-18 21:26 ` Cook, Malcolm
2015-11-22 10:53 ` Andreas Enge
2015-11-23 15:00 ` Ludovic Courtès
2015-11-23 15:29 ` Mathieu Lirzin
2015-11-23 19:38 ` John Darrington
2015-11-24 12:05 ` Alex Sassmannshausen
2015-11-24 14:54 ` Efraim Flashner
2015-11-24 15:12 ` John Darrington
2015-11-24 15:12 ` Ricardo Wurmus
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=87618o6l7y.fsf@netris.org \
--to=mhw@netris.org \
--cc=guix-devel@gnu.org \
--cc=pjotr.public12@thebird.nl \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).