Version-Release number of selected component: fedmsg-notify-0.5.4-1.fc20 Additional info: reporter: libreport-2.2.3 cmdline: /usr/bin/python /usr/bin/fedmsg-notify-daemon dso_list: fedmsg-0.9.0-1.fc20.noarch executable: /usr/bin/fedmsg-notify-daemon kernel: 3.15.6-200.fc20.x86_64 runlevel: N 5 type: Python uid: 1000 Truncated backtrace: __init__.py:115:__init__:TypeError: 'str' object is not callable Traceback (most recent call last): File "/usr/bin/fedmsg-notify-daemon", line 9, in <module> load_entry_point('fedmsg-notify==0.5.4', 'console_scripts', 'fedmsg-notify-daemon')() File "/usr/lib/python2.7/site-packages/fedmsg_notify/daemon.py", line 349, in main service = FedmsgNotifyService() File "/usr/lib/python2.7/site-packages/fedmsg_notify/daemon.py", line 130, in __init__ fedmsg.consumers.FedmsgConsumer.__init__(self, moksha.hub._hub) File "/usr/lib/python2.7/site-packages/fedmsg/consumers/__init__.py", line 115, in __init__ current_proc().name(), TypeError: 'str' object is not callable Local variables in innermost frame: self: <fedmsg_notify.daemon.FedmsgNotifyService at /org/fedoraproject/fedmsg/notify at 0x2e75ed0> hub: <moksha.hub.hub.CentralMokshaHub object at 0x33401d0> name: 'FedmsgNotifyService' module: 'fedmsg_notify.daemon'
Created attachment 919758 [details] File: backtrace
Created attachment 919759 [details] File: environ
This is fixed upstream in this pull request: https://github.com/fedora-infra/fedmsg/pull/267 It should be fixed with the fedmsg-0.9.1-1 release. Can you confirm?
Verified fixed in fedmsg-0.9.3-1.fc20.noarch from updates-testing
Thanks Ryan.