Hi,

Using version 2.0.2 on a sid box, with the same key that I used in
post#2, I do get a different traceback, which seems unrelated:


Really sign key? [y/N] y
command: ['gpg', '--command-fd', '0', '--with-fingerprint',
'--list-options',
'show-sig-subpackets,show-uid-validity,show-unusable-uids,show-unusable-subkeys,show-keyring,show-sig-expire',
'--status-fd', '2', '--quiet', '--batch', '--fixed-list-mode',
'--no-tty', '--with-colons', '--use-agent', '--secret-keyring',
'/home/emilien/.gnupg/secring.gpg', '--homedir', '/tmp/pygpg-s5Sx9O',
'--sign-key', 'Stefano Zacchiroli <z...@debian.org>']
SKIPPED: [GNUPG:] KEYEXPIRED 1417438220
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 70, in
main
    self.sign_key()
  File "/usr/lib/python2.7/dist-packages/monkeysign/ui.py", line 305, in
sign_key
    if not self.tmpkeyring.sign_key(pattern, alluids):
  File "/usr/lib/python2.7/dist-packages/monkeysign/gpg.py", line 482,
in sign_key
    raise GpgRuntimeError(self.context.returncode, _('cannot select uid
for signing: %s') % e.found().decode('utf-8'))
monkeysign.gpg.GpgRuntimeError: [Errno 0] cannot select uid for signing:
[GNUPG:] KEYEXPIRED 1417438220


The weird thing is that neither my key (I just signed 3 other keys
without issues) nor the key that I'm signing have expired.

As I don't know if this traceback occurs before or after the place where
the original issue occurred, I can't really confirm if the issue is fixed.

Let me know if I can provide extra information for you to reproduce.
    +Emilien

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to