RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

This is the same issue as https://bugzilla.redhat.com/show_bug.cgi?id=1121240, but jinja2 is in base/updates on RHEL6, hence the separate issue. Please close and link to the original issue if I have done this in error.


Description of problem:

Missing dep results in jinja2.__version__ to evaluate to "unknown"

How reproducible:

100% of the time on a box without python-setuptools

Steps to Reproduce:
1. Install python-jinja2
2. Run the command: python -c 'import jinja2; print(jinja2.__version__)'

Actual results:

The command returns "unknown"

Expected results:

The command should return the version of Jinja2, "2.2.1"


I'm guessing this bug exists on RHEL7 too (though I haven't had a chance to test), should I file a separate bug for that?

This indeed is a bug and the suggested solution is correct - we should add python-setuptools as a runtime requirement to python-jinja2.
Note, that this is *not* a problem on RHEL 7, since in version 2.7.2, jinja doesn't specify version using setuptools anymore, but rather uses simple

__version__ = '2.7.2'

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2017-0635.html