From: ludo@gnu.org (Ludovic Courtès)
To: znavko <znavko@protonmail.com>
Cc: 32797@debbugs.gnu.org
Subject: bug#32797: gcrypt won't compile during 'guix pull'
Date: Sat, 22 Sep 2018 15:07:10 +0200 [thread overview]
Message-ID: <87wordvfy9.fsf@gnu.org> (raw)
In-Reply-To: <ODL5e6CjklDuF2lZCWy6qKLgls1EiRWSVVVikD2hCSxNL6VBv58D-zIwowGWd5c7Em9hYwn88izoL0Ch1VHgN1Q-U_DqiEDbGQffMlR1K18=@protonmail.com> (znavko's message of "Fri, 21 Sep 2018 09:54:26 +0000")
Hello znavko,
znavko <znavko@protonmail.com> skribis:
> The following derivations will be built:
> /gnu/store/d4r9mpqp5xa4k58akad1aq3xdcdbfabk-guix-e0b07ccc1-modules.drv
> /gnu/store/gmpr0hbdyy174bz0iijka994frabmnh5-config.scm.drv
> /gnu/store/328ckyk2a94jqrfms3g7kgxzwg44y2yb-guix-config.drv
> /gnu/store/33nzis2q60i8d2k6js0k95birzgnxzw7-guix-system.drv
> /gnu/store/8ncrx1h6piq3276z5914dx74v1sg6c6r-guix-config-source.drv
> /gnu/store/hgfcwzi8xjmf0nv5p7pln08bx7n30sw9-guix-packages.drv
> /gnu/store/nrc7qq93lh4j4qx3wwsvlp2g5j5n0g4z-guix-extra.drv
> /gnu/store/pib2zn4yxpxldq57x66wsjs50va0jlwy-guix-core-source.drv
> /gnu/store/rlm6rvar7c7c53mg38331l39s0mrdfzf-guix-cli.drv
> /gnu/store/rzpzsw9dj736gdvnvs0023lgc22jxxch-guix-packages-base.drv
> /gnu/store/x4f13g6ghwnxmdq143pzvhcbbakwipdk-guix-core.drv
> compiling... 100.0% of 38 files
> loading... 97.4% of 115 filesrandom seed for tests: 1537520378
> compiling... 100.0% of 115 files
> compiling... 100.0% of 1 files
> compiling... 100.0% of 233 files
> compiling... 100.0% of 180 files
> compiling... 100.0% of 68 files
> compiling... 100.0% of 40 files
> updated GNU Guix successfully deployed under `/root/.config/guix/latest'
>
> # guix list-generations
[...]
> ERROR: In procedure scm-error:
> no code for module (gcrypt hash)
The message by ‘guix pull’ shows that you were running a version of
‘guix pull’ that predates Guix 0.15.0. Version 0.15.0 introduced an
overhaul of ‘guix pull’, precisely to solve the kind of issues that you
experienced here.
The transition from pre-0.15.0 is inconvenient and goes along these
lines:
1. Run ‘guix pull’ like you already did;
2. Install guile-gcrypt by running:
guix package -i
/gnu/store/c58hm7wm8i5fwfckzb168bmiqa2nw3w9-guile-gcrypt-0.1.0
3. Re-run ‘guix pull’.
4. Make the new ‘guix’ available from the command-line:
export PATH=$HOME/.config/guix/current/bin:$PATH
hash guix
This last step gives you the latest post-0.15.0 ‘guix pull’. If you run
‘guix describe’, it should print you the commit currently used.
HTH!
Ludo’.
next prev parent reply other threads:[~2018-09-22 13:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-21 9:54 bug#32797: gcrypt won't compile during 'guix pull' znavko
[not found] ` <twuChfHjbujAeZHGIQZS0u1QDUyV4u4YPedYRQPoWIXlKUcPbCQHi368D4a0f6hJb5-qBUeSV1JXSsc882MNcsMCm08pKRQhoYamnV_KlrY=@protonmail.com>
2018-09-21 12:14 ` znavko
2018-09-22 13:07 ` Ludovic Courtès [this message]
2018-09-22 17:35 ` znavko
2018-09-23 19:50 ` Ludovic Courtès
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=87wordvfy9.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=32797@debbugs.gnu.org \
--cc=znavko@protonmail.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.
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).