Obvious benefit will be:

• It will be easier for developers who use pkg-config for their applications, and want to use gpgme. They can use pkg-config for gpgme.

Last week

• Consideration for pkg-config: T4085: Add support for pkg-config
  • Something like PoC script in Bourne Shell
• New PCB design: FST-01SZ, where SZ stands for ShenZhen

Last Week:

• For nPth, T3283: Set 'mym4_revision' to 0 if not a git repo
• libgpg-error build
• GnuPG gniibe/decryption-key branch, almost stable

Done for npth.

Last week

• Only some follow up

No, it is your fix: rG278d87465685: gpg: Clear the symmetric passphrase cache for encrypted session keys..
Please cherry pick it to 2.2 branch.

Fixed in master and 2.2 branch.

I found two more cases. Those are included in the fix.

Good catch. Thank you.

Last week:

• For T3101: GnuPG 2.2 cannot import secret keys from 1.4/2.0's secring.gpg directly (if it is expired by original expiration date), I was wrong. Because pubring.gpg is there, importing secring.gpg just works.
• More dirmnger fix, this case for TOR_PORT2, from the report to gnupg-users (for cygwin).

The cause is: ! in nsswitch.conf
This was fixed (2.2 branch) by rGd4c0187dd931: libdns: Hack to skip negation term. for GnuPG in Jan 2017.
I found it was fixed in the original libdns, and this fix is merged into rG20c289606f89: libdns: Sync to upstream. to GnuPG.

Last week:

• Fixed bugs in dirmngr
• Learned how ks-engine-hkp.c works
  • It's good to have a way flushing HOSTTABLE

GnuPG itself does that in in gnupg/g10/migrate.c. We need to fixed this.

Thank you for your feedback.

It's manually written one in Debian:
https://salsa.debian.org/debian/gnupg2/blob/debian/master/debian/gpg-check-pattern.1

I manually configure IPv6 only environment, and now (forthcoming 2.2.9), it works fine for me.
So, I move this state to Testing.

• dirmngr fix for --recursive-resolver: rG5b40338f1276: dirmngr: Fix recursive resolver mode.
  • After the release, we can ask using this mode not to use nameserver in /etc/resolv.con, but resolve by libdns directly
  • Possibly, these bug reports are related: T2968: gpg --search: Connection closed in DNS, T3168: dirmngr: gpg: keyserver receive failed: No keyserver available, T3517: dirmngr: retry without SRV due to buggy routers

Applied to 2.2 branch.

As written in T2438:

I think that this is same issue of T2438: dirmngr fails repeatedly with "invalid argument", without kicking the host from its list.
Merging.

For the problem in the last comment, it was fixed in T2928: stop fetching PTR records entirely.
For the original issue, it looks that EINVAL is returned by the system call of connect(2).
That's quite strange, but, it was possible for IPv6.

Good. I don't think there is any reason to select the ephemeral port in user space (by default).
So, I disabled the feature for all OSes.

I found dirmngr tries to bind some random port. It might be the cause.

Fixed in repo (master and 1.8 branch).

Thanks for your report.
You are right.
Simply getting the information for "rng-type" through gcry_rndjent_get_version will hang.

And 2.2 branch.

Fixed in master.