In line with the Mass Python 2 Package Removal [0], the following (sub)packages of python-jinja2 were marked for removal: * python2-jinja2 According to our query, those (sub)packages only provide a Python 2 importable module. If this is not true, please tell us why, so we can fix our query. Please remove them from your package in Rawhide (Fedora 32). Please don't remove packages from Fedora 31, it is past Beta Freeze. Please don't do this for Fedora 30/29 either, removing packages from a released Fedora branch is forbidden. As said in the change document, if there is no objection in a week, we will remove the package(s) as soon as we get to it. This change might not match your packaging style, so we'd prefer if you did the change. If you need more time, please let us know here. If you do the change yourself, it would help us a lot by reducing the amount of packages we need to mass change. We hope this doesn't come to you as a surprise. If you want to know our motivation for this, please read the change document [0]. [0] https://fedoraproject.org/wiki/Changes/F31_Mass_Python_2_Package_Removal
Note that python2-jinja2 is still needed to: - run beaker (already doesn't install) - build seqan2 (has a bcond that can disable that dependency) - build termy-qt (already fails to build due to some Python 2 problems) I'll CC the maintainers of those packages to see if they mind if we drop python2-jinja2.
I have test builds for beaker against Python 3 going out now.
Eamon, can we drop python2-jinja2?
python2-jinja2 is still needed by trac, see bz1737930.
(In reply to Miro Hrončok from comment #3) > Eamon, can we drop python2-jinja2? You can drop it. The Python 2 issues in termy-qt are all related to the bundled V8 library build process. Gonna try and get this sorted out soon, but you don't need to wait on me.
trac will likely get an exception and will keep pulling this in.