+ /usr/bin/python setup.py test
Traceback (most recent call last):
File "setup.py", line 78, in <module>
File "/usr/lib64/python2.6/distutils/core.py", line 152, in setup
File "/usr/lib64/python2.6/distutils/dist.py", line 975, in run_commands
File "/usr/lib64/python2.6/distutils/dist.py", line 995, in run_command
File "/usr/lib/python2.6/site-packages/setuptools/command/test.py", line 127, in run
File "/usr/lib/python2.6/site-packages/setuptools/dist.py", line 245, in fetch_build_eggs
File "/usr/lib/python2.6/site-packages/pkg_resources.py", line 550, in resolve
raise VersionConflict(dist,req) # XXX put more info here
pkg_resources.VersionConflict: (Jinja2 2.2.1 (/usr/lib64/python2.6/site-packages), Requirement.parse('Jinja2>=2.4'))
chyba: Špatný návratový kód z /var/tmp/rpm-tmp.cHEv0a (%check)
chyby sestavení RPM:
Špatný návratový kód z /var/tmp/rpm-tmp.cHEv0a (%check)
Could not execute local: Non zero exit
mitmanek:python-flask (el6) $
python-flask-0.7.2-1 could be built in EL-6 if the blocking bug is fixed.
Flask requires Jinja2 v2.4 or later. The python-jinja2 package is provided in the RHEL6 base repository at v2.2.1, and thus cannot be updated.
I had requested an EL6 tag sometime back for the python-flask package before I had realized that the older version of Jinja2 was in RHEL6 proper.
(In reply to comment #1)
> Flask requires Jinja2 v2.4 or later. The python-jinja2 package is provided in
> the RHEL6 base repository at v2.2.1, and thus cannot be updated.
See bug 757811 comment 1 ... I don't know whether it is possible python-jinja2 would be actually upgraded in RHEL-6, or whether we should hope for python-jinja26 in EPEL.
So, there is now python-sphinx10 works just fine and in bug 757895 we have now python-jinja2-26 just exactly to overcome this.
Hi, I've been looking at the EL6 branch for this since we're interested in using Flask in Fedora Infrastructure.
Now that python-jinja2-26 is out, Flask builds just fine on EL6, but I've found some issues with the %check portion of the spec so far:
1) While in %check, setup.py doesn't find python-jinja2-26 first, causing it to error out on a dependency issue. This is fixed by patching setup.py to have "__requires__ = ['Flask>=2.4']" at the top of the file.
2) A test fails:
FAIL: test_test_app_proper_environ (flask.testsuite.basic.BasicFunctionalityTestCase)
Traceback (most recent call last):
File "/builddir/build/BUILD/Flask-0.8/flask/testsuite/basic.py", line 722, in test_test_app_proper_environ
File "/builddir/build/BUILD/Flask-0.8/flask/testsuite/__init__.py", line 133, in assert_equal
return self.assertEqual(x, y)
AssertionError: 200 != 404
Apparently this test fails because EPEL's version of Werkzeug is too old, and Flask's setup.py incorrectly states this.
I'm going to keep working on fixing these packaging issues. If anyone has a problem with me just committing fixes to the package git repo, let me know.
Proposed upgrade to python-werkzeug-0.8.3 to epel-devel:
The policy in question is here:
I've been working on this with Ian today.
The current plan is to get Flask 0.9 in EPEL 6.
We have two small patches that are necessary to make this work as painlessly as possible on RHEL 6. We'll be committing those soon.
The other blocker, as Ian said, python-werkzeug. We have 0.8.3 working fine on RHEL 6, and we can build that for EPEL as soon as the approval Ian mentioned goes through (likely at the next EPEL meeting).
python-flask-0.9-1.el6 has been submitted as an update for Fedora EPEL 6.
* should fix your issue,
* was pushed to the Fedora EPEL 6 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=epel-testing python-flask-0.9-1.el6'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
python-flask-0.9-4.el6 has been submitted as an update for Fedora EPEL 6.
python-flask-0.9-5.el6 has been submitted as an update for Fedora EPEL 6.
python-flask-0.9-5.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.