was 'Jinja2 python2 ends in error', now 'QtWebEngine does not need Jinja2'.
|Reported by:||Owned by:|
Not sure if this happens all the time, or mostly, or only randomly.
I initially reported this in http://lists.linuxfromscratch.org/pipermail/blfs-support/2020-May/082000.html but at that time a subsequent DESTDIR install appeared to work without problems.
A day or so ago, I hit the same problem on a fresh system.
Note that Jinja-2.11.2 is the last version that will support Python2, so trying to debug it seems like a waste of time when there is a workaround.
What seems to happen is that after Jinja has been installed for 2.7, easy_install looks at the runtime dependencies and decides that MarkupSafe is needed. With 2.11.1 I think it didn't install that for 2.7, but now - at least when the problem occurs - it tries to install the current version and that does not supprot python2.
|true' to the install (and to manually check that files in /usr/lib/python2.7/site-packages/Jinja2-2.11.2-py2.7.egg/jinja2/ have been installed).|
I'm proposing to include the workaround in the hope that jhalfs will not fail in this case.
For explanatory text:
Sometimes the python2 install tries to install the current version of MarkupSafe, and fails. As long as the files in /usr/lib/python2.7/site-packages/Jinja2-2.11.2-py2.7.egg/jinja2 have been installed, the install will be adequate for QtWebengine.
|true" : do not return an error status when the install apparently fails (to allow scripted installs).|
I'll note that the source has the following references to MarkupSafe:
MarkupSafe.Markup strings with an
./docs/intro.rst:As of version 2.7 Jinja depends on the
MarkupSafe_ module. If you install
./docs/intro.rst:.. _MarkupSafe: https://markupsafe.palletsprojects.com/
./CHANGES.rst:- Depend on MarkupSafe 0.23 or higher.
Also, I had the exact same problem when I first hit this and tried reverting to 2.11.1. Hmm, I had thought that MarkupSafe was unnecessary, but I see that in BLFS-9.1 it managed to install 1.1.1 for 2.7. Whatever, qtwebengine doesn't need it. Perhaps Python-2.7.18 broke something.
Change History (7)
comment:4 by , 2 years ago
|Status:||new → assigned|
|Summary:||Jinja2 python2 ends in error → was 'Jinja2 python2 ends in error', now 'QtWebEngine does not need Jinja2'.|