requestsync crashed with AssertionError in mailBug()

Bug #574060 reported by anatoly techtonik
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-dev-tools (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: ubuntu-dev-tools

requestsync should correctly handle missing GPG key, and probably check it before entering the request cycle.

gpg: no default secret key: secret key not available
gpg: [stdin]: clearsign failed: secret key not available
Traceback (most recent call last):
  File "/usr/bin/requestsync", line 228, in <module>
    mailBug(srcpkg, subscribe, status, title, report, options.keyid)
  File "/usr/lib/pymodules/python2.6/ubuntutools/requestsync/mail.py", line 184, in mailBug
    assert gpg.returncode == 0
AssertionError

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: ubuntu-dev-tools 0.99
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
CheckboxSubmission: 20db595a7600396752c39299ed2c326d
CheckboxSystem: daed2f3d6643b4a84b4520a2427f8c2b
Date: Mon May 3 02:04:17 2010
ExecutablePath: /usr/bin/requestsync
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/requestsync pydoctor lucid
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
PythonArgs: ['/usr/bin/requestsync', 'pydoctor', 'lucid']
SourcePackage: ubuntu-dev-tools
Title: requestsync crashed with AssertionError in mailBug()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
anatoly techtonik (techtonik) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #537288, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

tags: removed: need-duplicate-check
visibility: private → public
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.