From: Mark H Weaver <mhw@netris.org>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: 01/01: gnu: python-pygpgme: Use GnuPG 1 for the test suite.
Date: Wed, 27 Dec 2017 19:57:17 -0500 [thread overview]
Message-ID: <87lghnmzyq.fsf@netris.org> (raw)
In-Reply-To: <20171227020406.GA15719@jasmine.lan> (Leo Famulari's message of "Tue, 26 Dec 2017 21:04:06 -0500")
Leo Famulari <leo@famulari.name> writes:
> On Tue, Dec 26, 2017 at 07:11:13PM -0500, Mark H Weaver wrote:
>> > Author: Leo Famulari <leo@famulari.name>
>> > Date: Wed Dec 20 03:20:01 2017 -0500
>> >
>> > gnu: gpgme: Build with the latest GnuPG.
>> >
>> > * gnu/packages/gnupg.scm (gpgme)[inputs]: Use the latest gnupg package.
>> > [arguments]: Keep a reference to the gnupg package used for build.
>>
>> Clearly you were aware that python-pygpgme needed adjustment to continue
>> building, and I appreciate your attention to detail here, but something
>> seems to have gone wrong. Since these commits, Hydra has failed to
>> build python-pygpgme and python2-pygpgme on all hydra-supported systems:
>
> Thank you for bringing this to my attention.
>
> It's a consequence of having configured GPGME with --enable-fixed-path,
> which in our case forces GPGME to use the GnuPG executable it was built
> with. [0]
>
> I made this change rather late in the development of these patches,
> after having tested them more fully.
>
> Since we previously let GPGME find GnuPG in the environment, and that
> worked fine, I'll revert that part of the change shortly.
>
> [0] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=29781#25
Thanks for looking into it!
Alas, your most recent changes seem to have now broken qgpgme:
https://hydra.gnu.org/eval/109869#tabs-now-fail
https://hydra.gnu.org/job/gnu/master/qgpgme-1.9.0.x86_64-linux
https://hydra.gnu.org/job/gnu/master/qgpgme-1.9.0.i686-linux
https://hydra.gnu.org/job/gnu/master/qgpgme-1.9.0.armhf-linux
Mark
next prev parent reply other threads:[~2017-12-28 0:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20171220201341.6365.99040@vcs0.savannah.gnu.org>
[not found] ` <20171220201342.95BEC2044F@vcs0.savannah.gnu.org>
2017-12-27 0:11 ` 01/01: gnu: python-pygpgme: Use GnuPG 1 for the test suite Mark H Weaver
2017-12-27 2:04 ` Leo Famulari
2017-12-28 0:57 ` Mark H Weaver [this message]
2017-12-28 4:05 ` Leo Famulari
2018-01-07 2:19 ` Chris Marusich
2018-01-07 12:42 ` Marius Bakke
2018-01-08 2:57 ` Chris Marusich
2018-01-09 4:48 ` Leo Famulari
2017-12-28 4:56 ` Leo Famulari
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=87lghnmzyq.fsf@netris.org \
--to=mhw@netris.org \
--cc=guix-devel@gnu.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 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).