That's a fair point. However it's just not there in glibc (at least I couldn't
find it). But if that's the only offending part the first two hunks could just
be skipped.

Hi Werner,
the G_* stuff is from GLIB/GTK+ so for a GTK+ object it's what somebody would
expect. If you want to stay close to the rest of the pinentry coding style I'm
or course fine with that.

Here's the link to the GTK+ 3 transition:

D129: 294_0002-Add-gseal-gtk-compat.h-from-gedit.patch

Compat with older GTK+

D130: 293_0001-Make-DSEAL-safe.patch

This still affects 0.8.0.

Hi Marcus,
On Thu, Aug 13, 2009 at 01:29:26PM -0000, Marcus Brinkmann via BTS wrote:

Marcus Brinkmann <marcus@g10code.com> added the comment:

I don't see a reason to apply the patch, there are no po files generated for
pinentry. Is this to sync our copy of gtksecentry of another project? I
checked krb5-auth-dialog in Ubuntu, and it does not have this patch.

The patch is in krb5-auth-dialog's upstream. Ubuntu is lagging as
usual, Debian has it.

Any chance this gets applied?

D99: 234_0001-Don-t-mark-properties-as-translatable.patch

D83: 216_0001-don-t-install-gtk-entry-select-on-focus-settings-p.patch

D81: 214_0001-GtkSecureEntry-warning-fixes.patch

The coupling to secmem is why I propsed this for pinentry not for GTK+ itself.