Package: monkeysign
Version: 1.1
Followup-For: Bug #736120

Dear Maintainer,

I do get the same type of error when trying to sign one particular key
(ironically, Zack's).
I have today signed 15 other keys successfully without this problem.

This is the traceback I get (notice the different error message, containing
a newline at the end):

Really sign key? [y/N] y
Traceback (most recent call last):
  File "/usr/bin/monkeysign", line 41, in <module>
    u.main()
  File "/usr/lib/python2.7/dist-packages/monkeysign/cli.py", line 69, in
main
    self.sign_key()
  File "/usr/lib/python2.7/dist-packages/monkeysign/ui.py", line 296, in
sign_key
    if not self.tmpkeyring.sign_key(pattern, alluids):
  File "/usr/lib/python2.7/dist-packages/monkeysign/gpg.py", line 508, in
sign_key
    self.context.expect(proc.stderr, 'GOT_IT')
  File "/usr/lib/python2.7/dist-packages/monkeysign/gpg.py", line 243, in
expect
    return self.expect_pattern(fd, '^\[GNUPG:\] ' + pattern)
  File "/usr/lib/python2.7/dist-packages/monkeysign/gpg.py", line 235, in
expect_pattern
    raise GpgProtocolError(self.returncode, 'expected "%s", found "%s"' %
(pattern, line))
monkeysign.gpg.GpgProtocolError: [Errno 0] expected "^\[GNUPG:\] GOT_IT",
found "gpg: moving a key signature to the correct place
"
emilien@debiansid:~$


Thanks for your work on monkeysign!
    +Emilien

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.8-2-686-pae (SMP w/1 CPU core)
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 monkeysign depends on:
ii  gnupg                 1.4.16-1
ii  python                2.7.5-5
ii  python-pkg-resources  2.0.2-1

Versions of packages monkeysign recommends:
ii  python-gtk2       2.24.0-3+b1
ii  python-qrencode   1.01-3
ii  python-zbar       0.10+doc-9+b1
ii  python-zbarpygtk  0.10+doc-9+b1

monkeysign suggests no packages.

-- no debconf information

Reply via email to