PQM

traceback error when a valid-but-expired key is used

Bug #162263 reported by Robert Collins
2
Affects Status Importance Assigned to Milestone
PQM
Confirmed
High
Unassigned

Bug Description

 affects pqm

There appears to be a trivial bug in the way PQM handles signatures made
with
expired GPG keys.

----- Forwarded message from Bazaar Patch Queue Manager
<email address hidden> -----

Date: Sat, 10 Nov 2007 14:46:32 +0000 (GMT)
From: Bazaar Patch Queue Manager <email address hidden>
To: Andrew Bennetts <email address hidden>
Subject: error processing requests

An error was encountered:
Traceback (most recent call last):
  File "pqm/bin/pqm", line 218, in do_read_mode
    sigid,siguid = verify_sig(sender, msg, sig, 1, logger)
  File "/home/pqm/pqm/pqm/__init__.py", line 330, in verify_sig
    logger.info ("garh %s : %s", sig_from_key, sig_from_mail)
UnboundLocalError: local variable 'sig_from_key' referenced before
assignment

----- End forwarded message -----

-Andrew.

--
GPG key available at: <http://www.robertcollins.net/keys.txt>.

Changed in pqm:
status: New → Confirmed
importance: Undecided → High
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.