On Fri, 5 Jun 2015 09:06, d...@fifthhorseman.net said:
(cs, da, jp, fr, nl, pl, ru, sv, uk, and zh_TW appear to have
fuzzy-mapped Save in password manager to the Cancel string, which is
probably a pretty bad outcome; i agree that part should be fixed)
fuzzy marked entries are not used by
On Fri 2015-06-05 00:36:04 -0400, Michael Biebl wrote:
Am 05.06.2015 um 06:20 schrieb Daniel Kahn Gillmor:
If gnome-keyring can Depend: pinentry-gnome3 (#787786), it should be
able to build with --disable-gpg-agent.
I just installed pinentry-gnome3 to give it a try, but apparently it
needs
Am 05.06.2015 um 08:16 schrieb Daniel Kahn Gillmor:
make sense? does this work for you? please let me know if you're
having any trouble with it, i'm happy to help.
Seems to work ok for unlocking the keys. Haven't tried the Save in
password manager option yet, though.
That said, the package
On Fri 2015-06-05 02:39:55 -0400, Michael Biebl wrote:
That said, the package doesn't ship any translations apparently, and the
leading '_ in _Save, _OK and _Cancel look there is something broken
with i18n.
The _OK and _Cancel work fine in gcr under xfce4, as noted here:
Am 05.06.2015 um 08:39 schrieb Michael Biebl:
Am 05.06.2015 um 08:16 schrieb Daniel Kahn Gillmor:
make sense? does this work for you? please let me know if you're
having any trouble with it, i'm happy to help.
Seems to work ok for unlocking the keys. Haven't tried the Save in
password
Am 05.06.2015 um 09:06 schrieb Daniel Kahn Gillmor:
It looks to me like gcr_prompt_set_choice_label() doesn't support
prefixed-underscore accelerator keys the way
gcr_prompt_set_continue_label() and gcr_prompt_set_cancel_label() does
on xfce4's gcr.
Shall I open a bug in gcr about this?
On 05.06.2015 06:20, Daniel Kahn Gillmor wrote:
Control: retitle 760102 gnome-keyring: please build with --disable-gpg-agent
Control: block 760102 with 787786
On Thu 2015-06-04 22:30:21 -0400, Neal H. Walfield wrote:
At Thu, 04 Jun 2015 22:14:25 -0400, Daniel Kahn Gillmor wrote:
- An
Hi Stef,
At Fri, 05 Jun 2015 15:37:26 +0200,
Stef Walter wrote:
Confirming that I'll be ready to remove the code once the new pinentry
makes it into a release. Removing code always makes me smile :)
A new pinentry with the code has already been released (0.9.3).
:) Neal
--
To UNSUBSCRIBE,
Control: clone 760102 -1
Control: reassign -1 seahorse
Control: tags -1 + patch
Control: retitle -1 build seahorse compatible with gpg2
On Fri 2015-06-05 13:25:42 -0400, Michael Biebl wrote:
Am 05.06.2015 um 19:19 schrieb Daniel Kahn Gillmor:
Given that 1.4.7 is older than oldoldstable, you
On Fri, 5 Jun 2015 15:55, n...@walfield.org said:
A new pinentry with the code has already been released (0.9.3).
but you better get 0.9.4.
Salam-Shalom,
Werner
--
Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.
--
To UNSUBSCRIBE, email to
Am 05.06.2015 um 19:19 schrieb Daniel Kahn Gillmor:
Given that 1.4.7 is older than oldoldstable, you ought to be able to
drop the explicit gnupg dependency entirely from seahorse, iiuc.
Well, assuming that seahorse does work properly with gnupg2.
That's basically my question.
--
Why is it that
On Fri 2015-06-05 13:04:47 -0400, Michael Biebl wrote:
Just to be clear here: this new pinentry-gnome3 and gnupg-agent, do they
both work with either gnupg and gnupg2?
Yes, they both work with either gnupg or gnupg2.
@Joss: related to that, I notice, that you added a versioned dependency
on
Am 05.06.2015 um 15:55 schrieb Neal H. Walfield:
Hi Stef,
At Fri, 05 Jun 2015 15:37:26 +0200,
Stef Walter wrote:
Confirming that I'll be ready to remove the code once the new pinentry
makes it into a release. Removing code always makes me smile :)
A new pinentry with the code has already
Control: forwarded 787860 https://bugzilla.gnome.org/show_bug.cgi?id=750468
On Fri 2015-06-05 15:33:35 -0400, Michael Biebl wrote:
Since carrying patches downstream comes with a maintenance cost, we try
to avoid that as much as possible.
It thus would be great if you can forward this
On Fri, 05 Jun 2015 14:57:40 -0400 Daniel Kahn Gillmor
d...@fifthhorseman.net wrote:
On Fri 2015-06-05 13:25:42 -0400, Michael Biebl wrote:
Well, assuming that seahorse does work properly with gnupg2.
That's basically my question.
The seahorse source code seems to actually behave
Forgot to comment on your question here:
Am 05.06.2015 um 21:33 schrieb Michael Biebl:
On Fri, 05 Jun 2015 14:57:40 -0400 Daniel Kahn Gillmor
(the attached patch touches both ./configure.ac and ./configure -- since
the package appears to be doing autoreconf, maybe the modifications to
Am 05.06.2015 um 06:20 schrieb Daniel Kahn Gillmor:
If gnome-keyring can Depend: pinentry-gnome3 (#787786), it should be
able to build with --disable-gpg-agent.
I just installed pinentry-gnome3 to give it a try, but apparently it
needs further configuration to be used by gnome-keyring.
Can you
Control: retitle 760102 gnome-keyring: please build with --disable-gpg-agent
Control: block 760102 with 787786
On Thu 2015-06-04 22:30:21 -0400, Neal H. Walfield wrote:
At Thu, 04 Jun 2015 22:14:25 -0400, Daniel Kahn Gillmor wrote:
- An update to Gnome-Keyring that disables it GPG Agent
18 matches
Mail list logo
