FWIW, due to organizational matters we won't be able to handle donation dedicated to a certain task.
What we will do is to consider suggestions on which subproject to prioritize.

Good catch. Only on Windows64 sizeof(int)==sizeof(long) and thus the generic definition does not work.
Fixed in master and 1.7: rC7a339b1fc94cbda738cf7712830e783faa0e325e

Which version of gpgol (or Gpg4win) are you using?

Sorry, I can't access the build output (probably JS riddled paged). Please attach the config.log here.
In case you are building _on_ Windows: We do not support this - it may or may not work. All builds need to be done using a cross compiler from a Unix system.

Paypal now works and for accounts which can't do recurring donations; they are send back to the donation form now.

DSA is signature-only but VS-NfD is only about encryption. Thus signatures are out of scope. Even key management is out of scope. OTOH, certain algorithms are simply not allowed. This means we can't use SHA-1 except for specified and approved usages (in our case OpenPGP fingerprints).

Yes. mark them as non-compliant.

done. See
rD760d5feb22db7209bdc1f67bdc804b522da9df09

I was about to suggest that. However, please keep the code but disabled only the filling of the cache. And keep this open so that I can look for a real solution.

See kerckhoffs:~wk/ST-Gpg4VSNfD-v0.6.pdf - eventually this will be published but right now we don't have clearance from the BSI to do that.

g10/misc.c:gnupg_pk_is_compliant is my take on puble key algorithms. For cipher algorithm, we will only allow AES* and digest SHA-2-*. Other details are in a document we have in an project internal wiki - I'll send you a copy.

I thought about this but in the end it is unlikely that we will see request for other protection profiles. Thus I did spend a single bit on the German thing. Further, it is quite possible that a message matches several profiles and than bit fields come really handy. For the very limited circle of users a dedicated sub system for such things would be overkill.

Dirmngr uses its own resolver for these reasons:

See also rGde3a0988ef9addccd6b5c7950fb8797afbc3978d

Let me quote from the man page:

Sure. If will explain where to find newer entries.

I understand. What do you think of putting a few lines on top similar to

Mostly done now.

Disregard item b) from my commit message. procdonate handles this weel; i mixed that up with mkkudos.sh which is not able to handle this (because is modifies the source and does not use the source as a template as procdonate does it).

We tentatively decided to use an account of the local savings bank (KSD).

Is this still an issue for 2.1.21?

Great that we have the video finished. Some minor corrections are required, though:

Both GPL versions require:

The GPL requires us to keep and distribute ChangeLogs. Thus we can't remove them from the source tree.

According to @MFPA still a problem on 2.1.21.

Indeed and that is a standard feature of 2.1. It is even by default enabled. See --extra-socket in the the gpg-agent man page.

Ha, I need to use 2-23/3 to a run a job every 3 ours and not just 2/3.
Unfortunately the default cron logging does not log faulty log files. Changed that as well.