On Thu 2025-03-13 19:24:59 +0100, Guilhem Moulin wrote: > On Wed, 12 Mar 2025 at 15:13:03 -0400, Daniel Kahn Gillmor wrote: >> On Wed 2025-03-12 18:13:49 +0100, Andreas Metzler wrote: >>> php-crypt-gpg 1.6.9-3 can be built against gnupg 2.2.46-1 but fails >>> against gnupg 2.2.46-3 and later. And vice versa the patched testsuite >>> of php-crypt-gpg 1.6.9-4 only works with gnupg 2.2.46-3 (or similarily >>> patched versions of 2.4). >> >> yes, i think that's correct. If you'd prefer, i can offer a patch to >> php-crypt-gpg's test suite that accepts whether there's a trailing >> newline or not. That kind of flexible patch could be upstreamable, and >> would work with a patched or non-patched GnuPG. > > FWIW, as a current php-crypt-gpg uploader I don't mind having to > maintain such trivial patch to the test suite in order to fix FTBFS with > Debian's gpg. Wouldn't mind a more complex upstreamable patch of > course, but I don't consider this to be a blocker.
I've just written a more flexible patch and submitted it upstream as well: https://github.com/pear/Crypt_GPG/pull/40 I'm going to push this as php-crypt-gpg 1.6.9-5 -- hopefully this will help the packages transition smoothly without requiring us to keep a non-compliant GnuPG in debian. --dkg
signature.asc
Description: PGP signature
