On Mon, 2020-08-03 at 15:48 +0100, Dominic Hargreaves wrote: > This seems related to changes in libgnupg-interface-perl, which on > the > face of it is ignoring the instruction to use 'gpg1' (configured via > the test_gnupg_interface_gpg1.diff patch). I can't immediately see > why > that's happening but it seems related to the recent changes > libgnupg-interface-perl. > > Andrew, any clues?
Yes, this is related. I hadn't spotted it because I have both gpg and gpg1 installed on my workstation. If gpg isn't present, then I can reproduce this. The issue is with how GnuPG::Interface checks for the version of the gpg binary that is being run. A minor change to RT::Crypt::GnuPG in RT fixes this. I've written the patch to resolve this bug, pushed it to Salsa and raised a bug with Best Practical: https://rt.bestpractical.com/SelfService/Display.html?id=36623 I also find it a little puzzling though, I've checked the source in unstable and the patch name is test_gnupg-interface_gpg1.diff but the name of the patch used in the build log is test_gnupg- interface_gnupg.diff . This isn't in git, bullseye or unstable. Cheers, Andrew -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz | Catalyst Cloud: | This space intentionally left blank https://catalystcloud.nz |