Bug 459268

Summary: egg info for python-sqlobject
Product: [Fedora] Fedora EPEL Reporter: Jeffrey Tadlock <jeffreyt>
Component: python-sqlobjectAssignee: Luke Macken <lmacken>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: el5CC: a.badger, fschwarz, pfrields
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-11-11 02:40:01 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:

Description Jeffrey Tadlock 2008-08-15 14:51:21 UTC
Description of problem:

python-sqlobject-0.9.2-1.el5 appears to need to provide egg info to play nicely with TurboGears-1.0.4 that is also in EPEL.  pkg_resources.require() checks for sqlobject fail, though you can import and use sqlobject from a python interactive shell.

It appears fedora versions of python-sqlobject were updated to provide this information for this very reason.

From update log for python-sqlobject-0.9.3-2.fc8:

"Update Information:

SQLObject needs to provide egg-info in order for TG-1.0.4 to work.    I plan on
pushing this to stable pretty quickly.  I'll try to get people to test it ASAP."



Version-Release number of selected component (if applicable):

python-sqlobject-0.9.2-1.el5


How reproducible:

Steps to Reproduce:
1.  install TurboGears which will pull in python-sqlobject
2.  import pkg_resources; pkg_resources.require('sqlobject')
3.  returns the package cannot be found.
  
Actual results:

Package cannot be found, there is not an egg-info directory for sqlobject.

Expected results:

expect pkg_resources.require('sqlobject') to work

Additional info:

Running on CentOS 5.2

Comment 1 Luke Macken 2008-08-27 15:55:39 UTC
I just built python-sqlobject-0.9.7-1.el5, which should fix this issue.  It's currently in the needsign queue, and will be released in the next EPEL push.

Comment 2 Luke Macken 2008-11-11 02:40:01 UTC
This was fixed a while ago.