[pkg-gnupg-maint] Bug#788983: Bug#788983: Bug#788983: Bug#788983: missing translations in pinentry-gnome3

[Daniel Kahn Gillmor]

On Wed 2015-07-01 06:05:41 -0400, Werner Koch wrote:

> after the debug session yesterday we found the problem: The translation
> was not switched to the LC_MESSAGES value as received from gpg.  Thus
> the gpg-agent displayed static strings in it own locale while displaying
> strings received from gpg (description of the key) in gpg's locale.
>
> The fix was not trivial but fianlly I am able to switch gpg's locale at
> will and Pinentry shows the correct translation.  I have commited this
> to master and it will go into 2.1.6.
>
> The question is whether the work and possible breakage of backporting
> this to 2.0 is justified.  This bug has been around for about a decade
> but was not really noticed.  Thus, I would suggest not to backport it to
> 2.0.

Right.  This bug only affects users who have a gpg-agent that is running
in a different locale from their current login session, which is an
unusual case.  For single-user machines, the machine itself is usually
set to the desired locale, and the user has no variation.

For pre-2.1.6 releases on the 2.1 branch, for systems where a user might
vary locales between sessions, there is a simple workaround for the
situation where they find a gpg-agent sending prompts from the wrong
locale:

   gpgconf --kill gpg-agent

(the new agent will be restarted with the locale of the current
session).

For people running a 2.0 agent, there is no comparably simple
workaround.

However, i'm not convinced that this failure mode happens often enough
or is bad enough to warrant extra changes to the 2.0 branch.

Thanks for fixing this, Werner!

        --dkg