From: Chad Dougherty <crd@acm.org>
To: corinna-cygwin@cygwin.com,
"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: resolv.conf and gnupg2
Date: Mon, 8 Aug 2022 14:29:42 -0400 [thread overview]
Message-ID: <8795f150-f506-7772-5d34-b1e8957892b1@acm.org> (raw)
In-Reply-To: <YvEZ+JKAmCG7SLrN@calimero.vinschen.de>
Corinna Vinschen wrote:
>
> IIUC, that should be fixable by configuring gnupg with --disable-libdns.
>
Yes, below is the message that I sent to Marco but which was rejected by
this list because I wasn't subscribed at the time that I replied to all.
--
-Chad
On 2022-08-07 10:34, Marco Atzeri wrote:
> Any suggestion on how to solve the absence of /etc/resolv.conf ?
> I doubt gnupg2 is the proper package to do so.
>
Looking into this, I'm reminded of how much I really dislike the design
of gnupg2.
dirmngr appears to have its own DNS client library that tries to do the
resolv.conf parsing among other things. I believe this library gets
compiled into the current cygwin package.
I noticed this configuration option:
--disable-libdns do not build with libdns support
I just tested a build using this option and it seemed to fix the problem
for me.
I did not use the full end-to-end cygport process but I think the patch
at the bottom of this message should do the trick. Could you give it a
shot?
Thanks...
--
-Chad
$ diff -u gnupg2.cygport.orig gnupg2.cygport
--- gnupg2.cygport.orig 2022-08-08 14:00:18.562073400 -0400
+++ gnupg2.cygport 2022-08-08 14:00:53.146950000 -0400
@@ -22,6 +22,6 @@
cygautoreconf
sed -i -e '/^development_version=/s/yes/no/' configure
cd ${B}
- cygconf --enable-gpg-is-gpg2
+ cygconf --enable-gpg-is-gpg2 --disable-libdns
cygmake
}
next prev parent reply other threads:[~2022-08-08 18:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-07 14:34 Marco Atzeri
2022-08-07 22:33 ` Mark Geisert
2022-08-08 9:15 ` ASSI
2022-08-08 11:50 ` Corinna Vinschen
2022-08-08 7:30 ` Corinna Vinschen
2022-08-08 11:54 ` Corinna Vinschen
2022-08-08 12:13 ` Yasuhiro Kimura
2022-08-08 14:13 ` Corinna Vinschen
2022-08-08 18:29 ` Chad Dougherty [this message]
2022-08-10 17:22 ` 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=8795f150-f506-7772-5d34-b1e8957892b1@acm.org \
--to=crd@acm.org \
--cc=corinna-cygwin@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).