abrt 1.1.1 detected a crash. architecture: x86_64 cmdline: /usr/bin/python /usr/bin/fedpkg build component: fedora-packager executable: /usr/bin/fedpkg kernel: 2.6.33.6-147.fc13.x86_64 package: fedora-packager-0.5.1.0-1.fc13 reason: fedpkg:117:display_state:TypeError: 'NoneType' object is unsubscriptable release: Fedora release 13 (Goddard) backtrace ----- fedpkg:117:display_state:TypeError: 'NoneType' object is unsubscriptable Traceback (most recent call last): File "/usr/bin/fedpkg", line 959, in <module> args.command(args) File "/usr/bin/fedpkg", line 326, in build return _watch_koji_tasks(mymodule.kojisession, [task_id], quiet=args.q) File "/usr/bin/fedpkg", line 229, in _watch_koji_tasks for t in tasks.values() if not t.is_done()])) File "/usr/bin/fedpkg", line 117, in display_state if info['state'] == koji.TASK_STATES['OPEN']: TypeError: 'NoneType' object is unsubscriptable Local variables in innermost frame: info: None self: <__main__.TaskWatcher object at 0x2bb1e10> comment ----- $ fedpkg build Created task: 2376017 Task info: http://koji.fedoraproject.org/koji/taskinfo?taskID=2376017 Watching tasks (this may be safely interrupted)... ^CTraceback (most recent call last): File "/usr/bin/fedpkg", line 959, in <module> args.command(args) File "/usr/bin/fedpkg", line 326, in build return _watch_koji_tasks(mymodule.kojisession, [task_id], quiet=args.q) File "/usr/bin/fedpkg", line 229, in _watch_koji_tasks for t in tasks.values() if not t.is_done()])) File "/usr/bin/fedpkg", line 117, in display_state if info['state'] == koji.TASK_STATES['OPEN']: TypeError: 'NoneType' object is unsubscriptable How to reproduce ----- 1. Update package 2. run fedpkg build 3. press ctrl+c when it says" Watching tasks (this may be safely interrupted)..."
Created attachment 436194 [details] File: backtrace
Ok, pretty simple to trap ^c here. I had assumed the koji library would do it for me, guess not.
Hrm, I'm not able to reproduce this by a simple ^c. Are you able to reliably reproduce this?
Thought I updated this, but I was able to reproduce and I've patched it to work.
*** This bug has been marked as a duplicate of bug 620465 ***