unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 29781-done@debbugs.gnu.org
Subject: [bug#29781] [PATCH 1/2] gnu: gpgme: Build with the latest GnuPG.
Date: Wed, 20 Dec 2017 16:43:13 -0500	[thread overview]
Message-ID: <20171220214313.GA13511@jasmine.lan> (raw)
In-Reply-To: <871sjpy1em.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 675 bytes --]

On Wed, Dec 20, 2017 at 02:28:01PM +0100, Ludovic Courtès wrote:
> Leo Famulari <leo@famulari.name> skribis:
> 
> > * gnu/packages/gnupg.scm (gpgme)[inputs]: Use the latest gnupg and make
> > it a native-input.
> 
> I’m surprised gpgme doesn’t retain a reference to gpg.
> 
> Apparently, ‘dirinfo.gpg_name’ in src/dirinfo.c contains the file name
> of the ‘gpg’ executable.
> 
> I can’t find what its default value is, but I think we should be
> recording the absolute file name of ‘gpg’ as the default value.
> 
> Thoughts?

Good point. I pushed 0e06bec250f which uses the latest GnuPG package and
makes GPGME use that particular GnuPG.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2017-12-20 21:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-20  8:30 [bug#29781] GnuPG 2.0 end-of-life Leo Famulari
2017-12-20  8:32 ` [bug#29781] [PATCH 1/2] gnu: gpgme: Build with the latest GnuPG Leo Famulari
2017-12-20  8:32   ` [bug#29781] [PATCH 2/2] gnu: python-pygpgme: Use GnuPG 1 for the test suite Leo Famulari
2017-12-20 13:29     ` Ludovic Courtès
2017-12-20 20:15       ` bug#29781: " Leo Famulari
2017-12-20 22:26         ` [bug#29781] " Ludovic Courtès
2017-12-20 13:28   ` [bug#29781] [PATCH 1/2] gnu: gpgme: Build with the latest GnuPG Ludovic Courtès
2017-12-20 21:43     ` Leo Famulari [this message]
2017-12-27  5:04       ` 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=20171220214313.GA13511@jasmine.lan \
    --to=leo@famulari.name \
    --cc=29781-done@debbugs.gnu.org \
    --cc=ludo@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).