Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1246859 - Unable to import _fedora module
Summary: Unable to import _fedora module
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: fedmsg-notify
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Fedora Infrastructure SIG
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1299132 1308819 1357034 1377688 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-26 12:26 UTC by Ben Boeckel
Modified: 2017-08-08 12:02 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-08 12:02:44 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Ben Boeckel 2015-07-26 12:26:07 UTC 
Description of problem:
In [1]: import fedmsg_notify.distro_specific._fedora
---------------------------------------------------------------------------
ImportError                               Traceback (most recent call last)
<ipython-input-1-84ae77aa8a9a> in <module>()
----> 1 import fedmsg_notify.distro_specific._fedora

/usr/lib/python2.7/site-packages/fedmsg_notify/distro_specific/_fedora.py in <module>()
     20 
     21 import yum
---> 22 import problem
     23 from fedora.client.pkgdb import PackageDB
     24 

ImportError: No module named problem

Missing a Requires: somewhere. Looks like abrt-python?

Version-Release number of selected component (if applicable):
fedmsg-notify-0.5.5-3.fc23.noarch
Comment 1 Tom Prince 2015-10-30 04:31:18 UTC 
I can confirm that installing abrt-python allows fedmsg-notify-config to start.
Comment 2 Jan Kurik 2016-02-24 13:28:35 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle.
Changing version to '24'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase
Comment 4 Kevin Fenzi 2016-09-25 19:04:25 UTC 
*** Bug 1308819 has been marked as a duplicate of this bug. ***
Comment 5 Kevin Fenzi 2016-09-25 19:05:23 UTC 
abrt-python doesn't seem to fix things here. ;( 

Or there's some futher dep I don't see... will dig more
Comment 6 Kevin Fenzi 2016-09-25 19:06:29 UTC 
*** Bug 1357034 has been marked as a duplicate of this bug. ***
Comment 7 Aurelien Bompard 2016-12-12 17:05:42 UTC 
I've updated the spec file to require abrt-python, since it fixes the problem here too. Kevin, if it still breaks for you, could you please reopen this bug with a traceback? Thanks!
Comment 8 Aurelien Bompard 2016-12-12 17:06:56 UTC 
*** Bug 1299132 has been marked as a duplicate of this bug. ***
Comment 9 Aurelien Bompard 2016-12-12 17:07:19 UTC 
*** Bug 1377688 has been marked as a duplicate of this bug. ***
Comment 10 Fedora Update System 2016-12-12 17:07:43 UTC 
fedmsg-notify-0.5.5-6.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2016-098467dfc5
Comment 11 Fedora Update System 2016-12-13 05:31:29 UTC 
fedmsg-notify-0.5.5-6.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-098467dfc5
Comment 12 Paul W. Frields 2016-12-14 14:01:55 UTC 
I'm still getting a tb here: https://paste.fedoraproject.org/506261/24000148/
Comment 13 Fedora Update System 2016-12-14 15:20:14 UTC 
fedmsg-notify-0.5.6-1.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2016-083bb3017a
Comment 14 Paul W. Frields 2016-12-14 19:14:51 UTC 
Sorry to be a PITA. If I flip the notifications "On" using the control, I now see this error on CLI:

org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.fedoraproject.fedmsg.notify exited with status 1

No "bus" icon appears in the Shell.
Comment 15 Paul W. Frields 2016-12-14 19:15:12 UTC 
I'm using the new 0.5.6-1 build, by the way.
Comment 16 Fedora Update System 2016-12-15 05:08:10 UTC 
fedmsg-notify-0.5.6-1.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-083bb3017a
Comment 17 Fedora Update System 2017-02-15 16:04:58 UTC 
fedmsg-notify-0.5.7-1.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-b78dcc00b5
Comment 18 Fedora Update System 2017-02-17 15:26:07 UTC 
fedmsg-notify-0.5.7-1.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-b78dcc00b5
Comment 19 Fedora End Of Life 2017-07-25 19:02:25 UTC 
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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 '24'.

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 24 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 20 Fedora End Of Life 2017-08-08 12:02:44 UTC 
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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
bug.

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.