Bug 461867

Summary: setroubleshoot-server cannot be started: incomplete renaming of socket -> Socket
Product: [Fedora] Fedora Reporter: Michel Lind <michel>
Component: setroubleshootAssignee: Daniel Walsh <dwalsh>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: jdennis, yaneti
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-09-11 17:50:38 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Patches access_control.py to use Socket consistently none

Description Michel Lind 2008-09-11 00:49:15 UTC
Created attachment 316382 [details]
Patches access_control.py to use Socket consistently

Description of problem:
In the most recent version of setroubleshoot-server, the Python socket library is imported as Socket; however, it is still used in two places as socket

Version-Release number of selected component (if applicable):
2.0.8-2.fc10

How reproducible:
Always

Steps to Reproduce:
1. /sbin/service setroubleshoot start

  
Actual results:
Does not start: name 'socket' is not defined

Expected results:
Should start

Additional info:
Patch attached. Incidentally, could the download URL for the tarball be included in the source, so that spectool -gf work?

Comment 1 Yanko Kaneti 2008-09-11 01:43:19 UTC
I believe this is fixed in 2.0.9
you can have the current latest (2.0.10) from koji
http://koji.fedoraproject.org/koji/buildinfo?buildID=62562

Comment 2 Daniel Walsh 2008-09-11 17:50:38 UTC
Yes fixed in 2.0.10