From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: gnupg2 ?
Date: Tue, 11 Jul 2017 21:12:00 -0000 [thread overview]
Message-ID: <2402b341-c7db-87f5-6f06-6721904017ac@cygwin.com> (raw)
In-Reply-To: <779290d3-a265-3ed1-ebe6-c582aaa876af@gmail.com>
On 2017-06-30 23:28, Marco Atzeri wrote:
> On 30/06/2017 22:20, Yaakov Selkowitz wrote:
>> On 2017-06-30 00:34, Marco Atzeri wrote:
>>> On 29/06/2017 08:27, Yaakov Selkowitz wrote:
>>>> In order to update gpgme, we need libassuan in the distribution, as
>>>> GnuPG 2 support is no longer optional. While I think we could get by
>>>> with just that (and allow it to fall back to 1.x support at
>>>> runtime), it
>>>> did spur me to take another look at the gnupg2 stack. I don't know if
>>>> it's *perfect* but it seems to be generally working:
>>>>
>>>> Any chance you could test this out and/or be interested in maintaining
>>>> some or all of it?
>>>
>>> I am uploading all except gpa, that will follow later.
>>
>> Great, thanks! Did you find anything else that needed changing in these
>> packages?
>
> only some DIFF_EXCLUDES
Based on feedback from the list, please consider the following:
https://github.com/cygwinports/pinentry/commit/b5933f33b4894849280e0edf88cac7883b9e10b0.patch
--
Yaakov
next prev parent reply other threads:[~2017-07-11 21:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-29 6:27 Yaakov Selkowitz
2017-06-29 10:17 ` Marco Atzeri
2017-06-30 5:34 ` Marco Atzeri
2017-06-30 19:22 ` Andrew Schulman
2017-06-30 20:01 ` Marco Atzeri
2017-06-30 20:21 ` Yaakov Selkowitz
2017-07-01 4:29 ` Marco Atzeri
2017-07-11 21:12 ` Yaakov Selkowitz [this message]
2017-07-12 4:52 ` Marco Atzeri
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=2402b341-c7db-87f5-6f06-6721904017ac@cygwin.com \
--to=yselkowitz@cygwin.com \
--cc=cygwin-apps@cygwin.com \
/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.
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).