From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: cygport upgrade to use gnupg2/gpg2 if available
Date: Tue, 25 Jun 2024 01:16:14 +0200 [thread overview]
Message-ID: <ed61ee4e-2a29-4bae-8450-0fa3f0ebdb09@gmail.com> (raw)
In-Reply-To: <05c9127e-7bf8-4cd1-bfe8-8d3357fadb73@SystematicSW.ab.ca>
On 25/06/2024 01:09, Brian Inglis via Cygwin-apps wrote:
> On 2024-06-24 16:23, Marco Atzeri via Cygwin-apps wrote:
>> On 26/11/2023 15:40, Jon Turney via Cygwin-apps wrote:
>>> On 21/11/2023 06:58, ASSI via Cygwin-apps wrote:
>>>> Brian Inglis via Cygwin-apps writes:
>>> But yeah, I think gpg2 obsoleting gpg, with compatibility symlinks is
>>> probably the right thing to do.
>
>> I will implement this in the next 2.4.5
>>
>> the current test version seems also able to correctly contact
>> keyservers. That was a problem on latest gpg2 package
>
> Yay! At last.
> That has been frustrating as I have been tweaking my keyserver configs
> in the hopes of getting the latest keys accepted for my package sources,
> other downloads, and scripts.
>
> I might be able to update and willing to adopt libxslt if all our gpg
> updates hang together.
>
test version for
gnupg2-2.4.5-1
libksba-1.6.7-1
are also up.
If you can also test
Regards
Marco
next prev parent reply other threads:[~2024-06-24 23:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 4:51 Brian Inglis
2023-11-21 6:20 ` Brian Inglis
2023-11-21 6:58 ` ASSI
[not found] ` <655c551b.0c0a0220.6dce4.7613SMTPIN_ADDED_BROKEN@mx.google.com>
2023-11-24 21:29 ` Marco Atzeri
2023-11-24 22:01 ` Brian Inglis
[not found] ` <38451.4474005968$1700549918@news.gmane.org>
2023-11-26 14:40 ` Jon Turney
2024-06-24 22:23 ` Marco Atzeri
2024-06-24 23:09 ` Brian Inglis
2024-06-24 23:16 ` Marco Atzeri [this message]
2024-06-25 5:38 ` Brian Inglis
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=ed61ee4e-2a29-4bae-8450-0fa3f0ebdb09@gmail.com \
--to=marco.atzeri@gmail.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).