From: Robert Vollmert <rob@vllmrt.net>
To: guix-devel@gnu.org
Subject: gcrypt import warnings
Date: Sat, 20 Jul 2019 12:03:54 +0200 [thread overview]
Message-ID: <C4070937-BDB3-464F-B595-0DFDE4E98609@vllmrt.net> (raw)
I’m getting the following warnings when running “make” in the guix repo:
WARNING: (guix scripts archive): `error-source' imported from both (gcrypt common) and (gcrypt pk-crypto)
WARNING: (guix scripts archive): `error-string' imported from both (gcrypt common) and (gcrypt pk-crypto)
Presumably introduced by the commit below; what was the reason for
the change?
commit 92ca25a32b4bd19cda563fa0807af0fa2d39e0e2
Author: Ludovic Courtès <ludo@gnu.org>
Date: Fri Jul 19 11:38:54 2019 +0200
guix archive: Use (gcrypt common).
* guix/scripts/archive.scm: Use (gcrypt common) for 'error-source' and
'error-string'.
next reply other threads:[~2019-07-20 10:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-20 10:03 Robert Vollmert [this message]
2019-08-22 21:26 ` gcrypt import warnings 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=C4070937-BDB3-464F-B595-0DFDE4E98609@vllmrt.net \
--to=rob@vllmrt.net \
--cc=guix-devel@gnu.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).