Package: assword
Version: 0.8-1
Severity: normal
assword initializes gpgme like this:
try:
gpg = gpgme.Context()
gpg.get_key(keyid)
except gpgme.GpgmeError:
print >>sys.stderr, "Invalid key ID:", keyid
sys.exit(20)
But it's entirely possible that the error raised has nothing to do
with the choice of keyid. (indeed, i just found a bug in the
intersection of the versions of gpgme and gnupg that i'm running that
causes an exception to be raised no matter what keyID is supplied).
The error message produced to the user should include some information
from the gpgme exception.
--dkg
PS in the use case that i found, the gpgme exception was just
gpgme.GpgmeError: (7, 16383, u'End of file')
which itself wasn't actually useful at all, but that's an issue to be
raised with python-gpgme (or perhaps gpgme itself) separately.
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing'), (200, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages assword depends on:
ii python 2.7.8-1
ii python-gpgme 0.3-1+b1
ii python-gtk2 2.24.0-4
ii python-pkg-resources 5.5.1-1
Versions of packages assword recommends:
ii python-xdo 0.2-2
ii xclip 0.12+svn84-4
assword suggests no packages.
-- debconf-show failed
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
