#53797 closed defect (fixed)
py27-jinja2 <2.9 breaks dependencies for ansible
| Reported by: | djp9803 (Dan Pollock) | Owned by: | adfernandes (Andrew Fernandes) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.4.1 |
| Keywords: | Cc: | blair (Blair Zajac), steenzout (Pedro Salgado), jmroot (Joshua Root) | |
| Port: | ansible py-jinja2 |
Description
The current version of ansible requires jinja2<2.9, but jinja2<2.9 is not available. This was made a requirement in ansible because jinja2(2.9) broke ansible.
When running a playbook containing templates using ansible 2.2.1.0.1, ansible reports: "The 'jinja2<2.9' distribution was not found and is required by ansible"
Further information: https://github.com/ansible/ansible/issues/20285
It seems that ansible needs to be updated (i believe upstream is already patched) or jinja2 needs to be reverted to <2.9.
Change History (4)
comment:1 Changed 8 years ago by mf2k (Frank Schima)
| Cc: | blair steenzout jmroot added |
|---|---|
| Keywords: | ansible jinja2 removed |
| Owner: | set to adfernandes |
| Port: | py-jinja2 added |
| Status: | new → assigned |
comment:2 Changed 8 years ago by adfernandes (Andrew Fernandes)
Okay - if I read the github issue correctly, the current jinja2-2.9.5 with ansible-2.2.2 should fix this, correct?
Since ansible-2.2.2 is currently in rc2 status, maybe the best thing to do is wait a week for it to be released, then this bug goes away?
comment:4 Changed 7 years ago by adfernandes (Andrew Fernandes)
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
In the future, please Cc the port maintainers (
port info --maintainers ansible), if any.