The update to dirmngr (et al) 2.1.18-1 fixes the resolve problem in dirmngr - at least for me.
It required a bit of fiddling: at first gpg2 --search-keys somekey would fail similarly as before, except that there is one more line in the output: "dirmngr is older than us" (2.1.17 < 2.1.18) Which, by the way, is not in the dirmngr log. I then did gpgconf --kill gpg-agent After which dirmngr and gpg2 seems to have resolved their version differences, since gpg2 --search-keys somekey returned the requested key. Thanks
