package gajim
severity 834399 normal
thanks
Okay, this is not an issue with GnuPG 2 breaking Gajim, but with Gajim
not being able to use GnuPG 2 properly. But then it is not serious, not
even important, but normal : main functionnality of Gajim, which is
instant messaging, it working fine,
On Thu, 18 Aug 2016 21:59, t...@mirbsd.de said:
> all agents, and logged in again) since the upgrade. This never was a
> problem before, and, considering both gpg and gnupg2 can still use the
> running/old agent, looks like it’s still no problem, so the warning is
> silly at best.
The warning is
Hi,
some general comments:
On Thu, 18 Aug 2016 16:36, d...@fifthhorseman.net said:
> ValueError: Unknown status message: u'KEY_CONSIDERED'
Gajim's state machine for the status lines should ignore all status
messages it does not know or need. We add new status lines every few
releases and it
tags 834399 - moreinfo
thanks
Daniel Kahn Gillmor dixit:
>Control: reassign 834399 gajim
>Control: retitle 834399 Gajim GnuPG improvements
>Control: tags 834399 + moreinfo
>Control: affects 834399 + gnupg
Please always Cc the maintainers of the package when reassigning,
as debbugs does NOT do
Control: reassign 834399 gajim
Control: retitle 834399 Gajim GnuPG improvements
Control: tags 834399 + moreinfo
Control: affects 834399 + gnupg
Hi Thorsten--
Thanks for the report, and for pointing out improvements that need to be
made in Gajim's handling of OpenPGP. I'm documenting different
5 matches
Mail list logo
