Expired GPG key for PQM user not handled gracefully
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
PQM |
Triaged
|
High
|
Unassigned |
Bug Description
If the GPG key for the user running PQM expires, all merge requests will fail with the following traceback:
gpg: no default secret key: unusable secret key
gpg: [stdin]: clearsign failed: unusable secret key
Traceback (most recent call last):
File "/home/
run(pqm_subdir, run_mode, queuedir, logger, logdir, mail_reply, mail_server, from_address, fromaddr, print_report)
File "/home/
do_
File "/home/
run_
File "/home/
(successes, unrecognized, output) = script.run()
File "/home/
command_result = command.run()
File "/home/
line='merge %s %s' % (self.from_branch, self.to_branch))
File "/home/
self.
File "/home/
tree.
File "<string>", line 4, in commit_write_locked
File "/home/
result = WorkingTree3.
File "<string>", line 4, in commit_write_locked
File "/home/
revprops=
File "/home/
self.rev_id = self.builder.
File "/home/
self.
File "<string>", line 4, in add_revision_
File "/home/
self.
File "<string>", line 4, in store_revision_
File "/home/
signature = gpg_strategy.
File "/home/
raise errors.
bzrlib.
The failure message sent to the submitter will be:
Failed to gpg sign data with command "['gpg', '--clearsign']"
Not a bug with the pqm software
status invalid