From: Mark H Weaver <mhw@netris.org>
To: Leo Famulari <leo@famulari.name>
Cc: Eric Bavier <ericbavier@openmailbox.org>, 22558-done@debbugs.gnu.org
Subject: bug#22558: gnupg-2.1.11 on x86_64 failed its tests many times on Hydra
Date: Sat, 13 Feb 2016 09:36:43 -0500 [thread overview]
Message-ID: <87oabkad8k.fsf@netris.org> (raw)
In-Reply-To: <20160213074118.GA24222@jasmine> (Leo Famulari's message of "Sat, 13 Feb 2016 02:41:18 -0500")
Leo Famulari <leo@famulari.name> writes:
> On Fri, Feb 12, 2016 at 10:02:32PM -0600, Eric Bavier wrote:
>> But I had to add "#:use-module (gnu packages)" to the
>> gnu/packages/gnupg.scm before it would build, otherwise "could not
>> find symbol search-path".
>
> Weird, that did not happen to me when building from 3a7261bf96b2 on
> x86_64 with a recent guix-daemon.
Eric presumably applied the patch to an older git checkout. It turns
out that #:use-module (gnu packages) was only added to gnupg.scm about a
week ago in commit a05d1d82c0.
Mark
next prev parent reply other threads:[~2016-02-13 14:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-04 15:28 Gnupg 2.1.11 Andreas Enge
2016-02-04 16:58 ` Ludovic Courtès
2016-02-04 19:36 ` Andreas Enge
2016-02-04 20:59 ` Mark H Weaver
2016-02-05 15:25 ` bug#22558: gnupg-2.1.11 on x86_64 failed its tests many times on Hydra Eric Bavier
2016-02-05 18:58 ` Leo Famulari
2016-02-07 20:50 ` Ludovic Courtès
2016-02-12 23:22 ` Mark H Weaver
2016-02-13 0:12 ` Leo Famulari
2016-02-13 2:13 ` Mark H Weaver
2016-02-13 4:02 ` Eric Bavier
2016-02-13 7:41 ` Leo Famulari
2016-02-13 7:46 ` Leo Famulari
2016-02-13 14:36 ` Mark H Weaver [this message]
2016-02-06 16:52 ` Gnupg 2.1.11 Alex Vong
2016-02-06 17:44 ` Mark H Weaver
-- strict thread matches above, loose matches on Subject: below --
2016-02-04 19:58 bug#22558: gnupg-2.1.11 on x86_64 failed its tests many times on Hydra Mark H Weaver
2016-02-04 20:22 ` Mark H Weaver
2016-02-04 20:40 ` Mark H Weaver
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=87oabkad8k.fsf@netris.org \
--to=mhw@netris.org \
--cc=22558-done@debbugs.gnu.org \
--cc=ericbavier@openmailbox.org \
--cc=leo@famulari.name \
/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.