I did a live install of Fedora 15 beta. Then I did a 'yum install grin' I then run grin, and I get this exception: Traceback (most recent call last): File "/usr/bin/grin", line 5, in <module> from pkg_resources import load_entry_point File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 2671, in <module> working_set.require(__requires__) File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 654, in require needed = self.resolve(parse_requirements(requirements)) File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 552, in resolve raise DistributionNotFound(req) pkg_resources.DistributionNotFound: argparse>=1.1 Is there a dependency missing in the rpm?
It does seem that I have argparse 1.1 installed: $ python -i Python 2.7.1 (r271:86832, Apr 12 2011, 16:15:16) [GCC 4.6.0 20110331 (Red Hat 4.6.0-2)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import argparse >>> argparse.__version__ '1.1'
I emailed the author of grin regarding this issue. Here is his response: > argparse got included into Python 2.7, so it doesn't have the > .egg-info information that pkg_resources uses to determine that the > dependency is satisfied. You can remove the dependency from the > setup.py safely. I do not control the RPM.
Thanks for your report. The fix seems simple, will have a look.
*** Bug 702750 has been marked as a duplicate of this bug. ***
grin-1.2.1-3.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/grin-1.2.1-3.fc15
Package grin-1.2.1-3.fc15: * should fix your issue, * was pushed to the Fedora 15 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing grin-1.2.1-3.fc15' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/grin-1.2.1-3.fc15 then log in and leave karma (feedback).
grin-1.2.1-3.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.