Bug 437912 – dev-python/starcluster-0.93.3 fails with non-matching module versions

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Richard Freeman 2012-10-11 00:59:34 UTC]

I'm getting errors when running starcluster if I don't have very specific versions of python modules installed:

Traceback (most recent call last):
  File "/usr/bin/starcluster-2.7", line 5, in <module>
    from pkg_resources import load_entry_point
  File "/usr/lib64/python2.7/site-packages/pkg_resources.py", line 2714, in <module>
    parse_requirements(__requires__), Environment()
  File "/usr/lib64/python2.7/site-packages/pkg_resources.py", line 585, in resolve
    raise DistributionNotFound(req)


Traceback (most recent call last):
  File "/usr/bin/starcluster-2.7", line 5, in <module>
    from pkg_resources import load_entry_point
  File "/usr/lib64/python2.7/site-packages/pkg_resources.py", line 2714, in <module>
    parse_requirements(__requires__), Environment()
  File "/usr/lib64/python2.7/site-packages/pkg_resources.py", line 585, in resolve
    raise DistributionNotFound(req)
pkg_resources.DistributionNotFound: decorator==3.3.1

These are not the most recent stable versions (at least on amd64), so starcluster will not run.

It seems like the sensible fix is to patch the program to not be quite so particular about versions.  Alternatively, the dependency needs to be to a specific version and not a >=.

Reproducible: Always

[Comment 1 Jeroen Roovers (RETIRED) 2012-10-11 02:59:27 UTC]

CC: 	[e-mail] did not match anything

Please fix cvs/gentoo-x86/dev-python/starcluster/metadata.xml

[Comment 2 Richard Freeman 2012-10-11 16:29:33 UTC]

FYI - the checks can be defeated by replacing == with >= in /usr/<libdir>/python2.7/site-packages/StarCluster-0.93.3-py2.7.egg-info/requires.txt

I can't say I've fully tested it with later versions.  However, the dependency spec in the requires file and the ebuild should match in any case.

[Comment 3 Ian Delaney (RETIRED) 2012-11-13 07:30:36 UTC]

The only package to object to changing >= to = in the ebuild is decorator.
Of the deps, only workerpool and jinja have only the one matching version in portage from which to choose.  The others have new versions which presumably will all be effective.
  
While it would preferable in principal to keep the list in requires.txt as is, It makes for the need to stabilize a decorator just to make it work, causing a  nuisance delay.  So let's sync these two, adjust only workerpool & jinja in the ebuild and the requires.txt to match, and you can consider making a stable req for decorator.

jtriley wrote initial ebuild.

[Comment 4 Richard Freeman 2012-11-13 08:18:57 UTC]

Did you actually intend to mark this resolved?  If so, it isn't exactly clear where we're going with this...

[Comment 5 Ian Delaney (RETIRED) 2012-11-13 12:36:12 UTC]

right.  Consider this a test request, and if all is well, that would warrant a state of resolved was my intent.  Thought it prudent to hold back from declaring resolved until a test proved fruitful.  Setting test-request to me this was implied

[Comment 6 JTRiley 2012-11-26 17:50:18 UTC]

Created attachment 330664 [details, diff]
fix version requirements in setup.py (not *egg.info/requires.txt)

The requires.txt patch didn't work for me - it applies but somewhere along the line StarCluster-0.93.3-egg.info/requires.txt gets re-written. I've attached a better "requires" patch that patches the setup.py file itself instead. It should be usable with the current 0.93.3 ebuild in portage. This patch will not be needed in the next release of StarCluster.

[Comment 7 Ian Delaney (RETIRED) 2012-11-30 08:29:00 UTC]

roger JTRiley, good 1. Patch applied. Fixed in portage 30 Nov.