From: George Clemmer <myglc2@gmail.com>
To: Alex Kost <alezost@gmail.com>
Cc: 32646@debbugs.gnu.org, "Clément Lassieur" <clement@lassieur.org>
Subject: bug#32646: emacs-guix doesn't build, because of guile-gcrypt
Date: Mon, 10 Sep 2018 11:14:45 -0400 [thread overview]
Message-ID: <877ejtz8nu.fsf@gmail.com> (raw)
In-Reply-To: <87zhwp4czw.fsf@gmail.com>
Alex Kost <alezost@gmail.com> writes:
> George Clemmer (2018-09-10 10:31 -0400) wrote:
>
>> Alex Kost <alezost@gmail.com> writes:
>>
>>> Ludovic Courtès (2018-09-06 11:09 +0200) wrote:
>>>
>>>>> ice-9/boot-9.scm:752:25: In procedure dispatch-exception:
>>>>> no code for module (guix hash)
>>>>> make[2]: [Makefile:556: emacs-guix/hash.go] Error 1 (ignored)
>>>>
>>>> I suppose Emacs-Guix might need to use (gcrypt hash) instead.
>>>> Any ideas, Alex?
>>>
>>> Ouch, there is no (guix hash) anymore.
>>
>> Looking at commit '57d70dbab * master origin/master gnu: Add yad.' it
>> seems that 'guix hash' is removed but still documented. Is a
>> re-implementation of 'guix hash' coming? Or is it the intent to remove
>> 'guix hash'. If so, ISTM this is be a meaningful loss of guix usability.
>
> No, no, the command "guix hash" did not go anywhere. It's just (guix
> hash) module that was removed. It was replaced by (gcrypt hash) module
> from "guile-gcrypt" package, which is a new dependency of Guix.
Ohh! DUH! Thanks for clarifying ;-) George
next prev parent reply other threads:[~2018-09-10 15:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-05 19:25 bug#32646: emacs-guix doesn't build, because of guile-gcrypt Clément Lassieur
2018-09-05 19:36 ` Clément Lassieur
2018-09-06 9:09 ` Ludovic Courtès
2018-09-06 9:09 ` Ludovic Courtès
2018-09-06 19:34 ` Alex Kost
2018-09-10 14:31 ` George Clemmer
2018-09-10 14:56 ` Alex Kost
2018-09-10 15:14 ` George Clemmer [this message]
[not found] ` <87r2i149j3.fsf@gmail.com>
2018-09-11 6:54 ` 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=877ejtz8nu.fsf@gmail.com \
--to=myglc2@gmail.com \
--cc=32646@debbugs.gnu.org \
--cc=alezost@gmail.com \
--cc=clement@lassieur.org \
/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).