[pkg-gnupg-maint] Behavioral change for pinentry-qt 1.2.0-1

[Gard Spreemann]

Daniel Kahn Gillmor <dkg at fifthhorseman.net> writes:

> It seems possible that the fact that 1.2.0-1 is built against a newer
> version of QT (because the build daemons have it available) could have
> caused the change you're seeing, but a *lot* has changed in the qt
> pinentry upstream between 1.1.0 and 1.2.0.  If you have a chance to do a
> bit more technical investigation, i'd consider running a simple test
> like this to observe whether a given pinentry behaves as you describe:
>
>      echo getpin | path/to/pinentry-qt
>
> And then use that test over a "git bisect" based on upstream's repo
> (https://dev.gnupg.org/source/pinentry.git), to see whether you can
> identify a specific commit that caused the difference.
>
> Whether you're able to identify the problem or not, you might want to
> open an issue on upstream's bugtracker (https://dev.gnupg.org/).  If you
> do that, please point to it here, i'd be interested in learning more.

Hi again,

I finally got around to this. Good news: The bisection showed me that
the problem is fixed upstream. I've filed #1013318 against pinentry-qt,
with an attached patch based on upstream's commits, and also an MR on
Salsa [1].

[1] https://salsa.debian.org/debian/pinentry/-/merge_requests/1


 Best,
 Gard

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 857 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-gnupg-maint/attachments/20220621/348a1ee8/attachment.sig>