Quick followup. The version that triggers this is at least 2.1.21[1]. I recall there was some wiggle room on minor versions before it. Thanks! -Santiago. [1] https://dev.gnupg.org/T3218 On Mon, Nov 13, 2017 at 06:02:02PM -0500, Santiago Torres wrote: > > > Were the ENOENT errors you encountered in running the tests multiple times > > easy to reproduce? > > If you had the right gpg2, it should be easy to repro with just re-running. > > > If so, I can certainly try to reproduce them and then > > run the tests with --reload in place of --kill to gpgconf. If that worked > > across the various gnupg 2.x releases, it would be a simple enough change to > > make as a follow-up. > > Let me dig up the exact versions. IIRC it was somewhere between 2.1.0 and 2.2.x > or so. I think somewhere within the patch re-rolls I had the exact versions. > > Cheers! > -Santiago.
Attachment:
signature.asc
Description: PGP signature
