Bug 1315317 - [abrt] fedmsg-notify: filters.py:24:<module>:ImportError: cannot import name get_reported_bugs
[abrt] fedmsg-notify: filters.py:24:<module>:ImportError: cannot import name ...
Product: Fedora
Classification: Fedora
Component: fedmsg-notify (Show other bugs)
x86_64 Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Fedora Infrastructure SIG
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2016-03-07 08:12 EST by piio
Modified: 2017-12-12 05:59 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2017-12-12 05:59:46 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (7.36 KB, text/plain)
2016-03-07 08:12 EST, piio
no flags Details
File: environ (824 bytes, text/plain)
2016-03-07 08:12 EST, piio
no flags Details

  None (edit)
Description piio 2016-03-07 08:12:43 EST
Version-Release number of selected component:

Additional info:
reporter:       libreport-2.6.4
cmdline:        /usr/bin/python /usr/bin/fedmsg-notify-daemon
dso_list:       python2-setuptools-20.1.1-1.fc24.noarch
executable:     /usr/bin/fedmsg-notify-daemon
kernel:         4.5.0-0.rc6.git2.2.fc25.x86_64
runlevel:       N 5
type:           Python
uid:            1000

Truncated backtrace:
#1 <module> in /usr/lib/python2.7/site-packages/fedmsg_notify/filters.py:24
#2 <module> in /usr/lib/python2.7/site-packages/fedmsg_notify/daemon.py:45
#3 resolve in /usr/lib/python2.7/site-packages/pkg_resources/__init__.py:2386
#4 load in /usr/lib/python2.7/site-packages/pkg_resources/__init__.py:2380
#5 load_entry_point in /usr/lib/python2.7/site-packages/pkg_resources/__init__.py:2720
#6 load_entry_point in /usr/lib/python2.7/site-packages/pkg_resources/__init__.py:547
#7 <module> in /usr/bin/fedmsg-notify-daemon:9

Potential duplicate: bug 1299132
Comment 1 piio 2016-03-07 08:12:47 EST
Created attachment 1133756 [details]
File: backtrace
Comment 2 piio 2016-03-07 08:12:49 EST
Created attachment 1133757 [details]
File: environ
Comment 3 Jan Kurik 2016-07-26 00:35:45 EDT
This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle.
Changing version to '25'.
Comment 5 Fedora End Of Life 2017-11-16 09:19:15 EST
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Comment 6 Fedora End Of Life 2017-12-12 05:59:46 EST
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.