Debian Patches
Status for pinentry/1.3.3-3
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| 0001-avoid-self-describing-as-a-beta.patch | avoid self-describing as a beta Using autoreconf against the source as distributed in tarball form invariably results in a package that thinks it's a "beta" package, which produces the "THIS IS A DEVELOPMENT VERSION" warning string. since we use dh_autoreconf, i need this patch to avoid producing builds that announce themselves as DEVELOPMENT VERSIONs. See discussion at: http://lists.gnupg.org/pipermail/gnupg-devel/2014-November/029065.html |
Daniel Kahn Gillmor <dkg@fifthhorseman.net> | no | 2015-05-13 | ||
| 0002-gtk2-When-X11-input-grabbing-fails-try-again-over-0..patch | gtk2: When X11 input grabbing fails, try again over ~0.4 seconds. * gtk+-2/pinentry-gtk-2.c (grab_keyboard): Delay 1 ms before retrying keyboard grab, limit to about 0.2 seconds. (grab_pointer): Delay 1 ms before retrying pointer_grab, limit to about 0.2 seconds. -- These changes were proposed by Vincent Bernat in https://bugs.debian.org/851707#124 |
Vincent Bernat <bernat@debian.org> | no | 2017-02-06 | ||
| 0003-gnome3-Redirect-GLib-logging-messages-to-stderr.patch | gnome3: Redirect GLib logging messages to stderr By default, GLib/Gcr/libsecret outputs debug/info logging messages to stdout, but we use that as the Assuan channel, and outputting to it anything but the expected verbs breaks pinentry pipelines in confusing ways. It is unknown whether a similar patch is needed for gtk-2 or other flavors via the 'CLEARPASSPHRASE' command, nor if G_MESSAGES_DEBUG needs unsetting from the environment. An old user reports Gtk-warnings even with pinentry-qt, but their issue needs more verification. https://web.archive.org/web/20260629091849/https://dev.gnupg.org/T4144.html Care must be placed in who inherits our Assuan fds and what they do with them. |
Kernc <kerncece@gmail.com> | no | 2026-08-18 |