From: Pjotr Prins <pjotr.public12@thebird.nl>
To: swedebugia <swedebugia@riseup.net>
Cc: guix-devel@gnu.org
Subject: Re: Adding a note to 3.6 Invoking guix pull
Date: Sun, 4 Nov 2018 11:44:59 +0100 [thread overview]
Message-ID: <20181104104459.wt5hvqu5no6cgaea@thebird.nl> (raw)
In-Reply-To: <c2389bcd-3cb7-e9ee-647b-6095578bef8d@riseup.net>
On Sun, Nov 04, 2018 at 10:47:39AM +0100, swedebugia wrote:
> Hi
>
> The more I use guix pull the less I feel like updating guix this way.
Have you tried fixating with the --commit option? I think that is
really important.
I do have the baffling issue that when I run two identical guix pulls
on two machines and use 'guix publish' on packages built using that
guix not all substitutes are available for the other. Maybe it has
something to do with the guix-daemon versions.
> I saw a long time ago a post from Ricardo about updating guix directly
> from the source tree.
>
> I think this way of updating guix should be written clearly in the
> manual and perhaps be noted in 3.6 Invoking guix pull
I have most success with using a build container for that. As
described in
https://gitlab.com/pjotrp/guix-notes/blob/master/INSTALL.org
(search for bullet).
> I think we need a whole new section between 3. and 4. titled "Upgrading
> Guix" with 2 subsections:
> 1. Invoking guix pull
> 2. Via guix source tree
>
> What do you think?
> --
> Cheers
> Swedebugia
prev parent reply other threads:[~2018-11-04 10:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-04 9:47 Adding a note to 3.6 Invoking guix pull swedebugia
2018-11-04 10:44 ` Pjotr Prins [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181104104459.wt5hvqu5no6cgaea@thebird.nl \
--to=pjotr.public12@thebird.nl \
--cc=guix-devel@gnu.org \
--cc=swedebugia@riseup.net \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.