Bug 1032645 - setroubleshoot needs a dep on python-report
Summary: setroubleshoot needs a dep on python-report
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: setroubleshoot
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Daniel Walsh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-20 14:15 UTC by Cole Robinson
Modified: 2013-11-26 04:53 UTC (History)
2 users (show)

Fixed In Version: setroubleshoot-3.2.14-2.fc20
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-26 04:53:26 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Cole Robinson 2013-11-20 14:15:16 UTC
Sealert gave me this error:

Traceback (most recent call last):
  File "/usr/bin/sealert", line 650, in <module>
    run_as_dbus_service(username)
  File "/usr/bin/sealert", line 109, in run_as_dbus_service
    app = SEAlert(user, dbus_service.presentation_manager, watch_setroubleshootd=True)
  File "/usr/bin/sealert", line 320, in __init__
    from setroubleshoot.browser import BrowserApplet
  File "/usr/lib64/python2.7/site-packages/setroubleshoot/browser.py", line 44, in <module>
    import report
ImportError: No module named report


Looks like setroubleshoot needs a dep on python-report

Comment 1 Daniel Walsh 2013-11-20 14:37:28 UTC
fixed in setroubleshoot-3.2.14-2.fc20

Comment 2 Cole Robinson 2013-11-20 14:47:42 UTC
Wait, I might have screwed this up. Double checking

Comment 3 Cole Robinson 2013-11-20 14:50:15 UTC
Yeah this is a bogus report. 1) the package is libreport-python, python-report doesn't exist. 2) setroubleshoot does seem to depend on it, though indirectly. but for whatever reason, libreport-python was installed on my machine but the module wasn't there. reinstall fixed it though.

So you should probably undo any change relating to 'python-report'. Sorry for the confusion.

Comment 4 Daniel Walsh 2013-11-20 14:57:05 UTC
setroubleshoot required libreport-gtk, which does not seem to bring in libreport-python.

rpm -q --requires setroubleshoot | grep report
libreport-gtk

 rpm -q --requires libreport-python | grep report
libreport = 2.1.9-1.fc21
libreport.so.0()(64bit)


I am not sure you are wrong.

Comment 5 Daniel Walsh 2013-11-20 14:57:54 UTC
yum remove libreport-python , does not attempt to remove setroubleshoot.

Comment 6 Cole Robinson 2013-11-20 15:03:59 UTC
Ah okay, I was afraid you took my request at face value and just added python-report to the spec.

Comment 7 Daniel Walsh 2013-11-20 15:15:19 UTC
Ordinarily I would,but I saw the requirement for libreport-gtk, and was surprised that it did not get the right stuff.  Then I investigated further.

Since abrt pulls in libreport-python, it is not a huge problem, but I will push out a fix when the package finished building.

Probably need fix in rhel7 also.

Comment 8 Fedora Update System 2013-11-20 15:19:26 UTC
setroubleshoot-3.2.14-2.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/setroubleshoot-3.2.14-2.fc20

Comment 9 Fedora Update System 2013-11-24 03:27:26 UTC
Package setroubleshoot-3.2.14-2.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing setroubleshoot-3.2.14-2.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-21915/setroubleshoot-3.2.14-2.fc20
then log in and leave karma (feedback).

Comment 10 Fedora Update System 2013-11-26 04:53:26 UTC
setroubleshoot-3.2.14-2.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.


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