AppVeyor continuous integration tests all fail with GPG errors

[rah2501]

It seems every pull request is failing with errors in the continuous integration tests related to importing the GPG key for David Macek [email protected]. For example:

:: Synchronizing package databases...
downloading mingw32.db...
downloading mingw32.db.sig...
error: mingw32: key "4A6129F4E4B84AE46ED7F635628F528CF3053E04" is unknown
:: Import PGP key 4096R/87771331B3F1FF5263856A6D974C8BE49078F532, "David Macek <[email protected]>", created: 2018-01-14? [Y/n] error: mingw32: signature from "David Macek <[email protected]>" is unknown trust
error: failed to update mingw32 (invalid or corrupted database (PGP signature))
downloading mingw64.db...
downloading mingw64.db.sig...
error: mingw64: signature from "David Macek <[email protected]>" is unknown trust
error: failed to update mingw64 (invalid or corrupted database (PGP signature))
downloading msys.db...
downloading msys.db.sig...
error: msys: signature from "David Macek <[email protected]>" is unknown trust
error: failed to update msys (invalid or corrupted database (PGP signature))
error: failed to synchronize all databases
Command exited with code 1
cat config.log
cat: config.log: No such file or directory
Command exited with code 1

Other examples:

https://ci.appveyor.com/project/stedolan/jq/builds/37026770/job/x6xltv5hp6miwx74

https://ci.appveyor.com/project/stedolan/jq/builds/36039851/job/1xkxtw6i9xqe5x2s

[itchyny]

Please consider merging #2193 with #2141.

[iainelder]

@rah2501 , @itchyny , have you had any feedback on this from the maintainers? The same CI failure is blocking even a simple dcumentation update in #2395 😞

[itchyny]

@iainelder Nope. I hope someone familiar with Windows help the maintainers to fix this release blocker.

[liquidaty]

FYI I am working on this, but #2589 is making it much more difficult than it should be.

If helpful, in that issue I've posted a modified YML which at least gets further than appveyor.yml and the windows.yml in the repo, to get the environment set up for a successful windows build (though whether the test failures are due to a bad build or faulty tests remains to be seen).