From: Ricardo Wurmus <rekado@elephly.net>
To: Hebi Li <lihebi.com@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: How to properly use channels? (my 'guix pull' throws error)
Date: Tue, 02 Oct 2018 21:42:40 +0200 [thread overview]
Message-ID: <87tvm4t9sf.fsf@elephly.net> (raw)
In-Reply-To: <87ftxo5fcu.fsf@gmail.com>
Hi,
> On Tue, Oct 02 2018, Ricardo Wurmus wrote:
>
>> AFAIK this defect has been fixed a couple of days ago. Unfortunately,
>> you need to upgrade Guix with “guix pull” but without channels. Once
>> upgraded you can use channels again.
>>
>
> I actually ran "guix pull" right before I tried Ludovic's suggestion
> earlier today. Anyway I pulled again, and did a full system upgrade
> (guix package -u) and also reconfigure (sudo -E guix system reconfigure
> config.scm), and even a reboot. The "guix pull" command is still
> complaining "no code for module (gcrypt hash)".
Could you please tell us which “guix” you are using? “guix pull”
installs a new Guix to ~/.config/guix/current/bin. Are you using Guix
from that directory?
> I thought ~/.config/guix/current symlink *is* the local source tree, and
> this document says both "./pre-inst-env guix pull" and "guix pull"
> upgrade it.
~/.config/guix is merely where “guix pull” installs new versions of
Guix. The source tree is wherever you run Guix via “pre-inst-env”.
--
Ricardo
next prev parent reply other threads:[~2018-10-02 19:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-27 2:31 How to properly use channels? (my 'guix pull' throws error) Hebi Li
2018-10-02 10:07 ` Ludovic Courtès
2018-10-02 18:10 ` Hebi Li
2018-10-02 18:22 ` Ricardo Wurmus
2018-10-02 19:16 ` Hebi Li
2018-10-02 19:42 ` Ricardo Wurmus [this message]
2018-10-02 20:11 ` Hebi Li
2018-10-02 20:19 ` 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=87tvm4t9sf.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=help-guix@gnu.org \
--cc=lihebi.com@gmail.com \
/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).