Summary: | dev-python/pbr-1.9.1 failed (compile phase): setup.py build: ImportError: No module named jinja2 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Bazz <mbazzinotti> |
Component: | Current packages | Assignee: | Matthew Thode ( prometheanfire ) <prometheanfire> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | openstack |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Bazz
2016-08-28 04:58:09 UTC
This is the only place in the repo that says jinja at all, so I don't think it's a problem with pbr. pbr/tests/test_setup.py:a65e8ee\x00Remove jinja pin.\x00 (tag: 0.5.14, tag: 0.5.13) and that's just part of a changelog (In reply to Matthew Thode ( prometheanfire ) from comment #1) > This is the only place in the repo that says jinja at all, so I don't think > it's a problem with pbr. > > pbr/tests/test_setup.py:a65e8ee\x00Remove jinja pin.\x00 (tag: 0.5.14, tag: > 0.5.13) > > and that's just part of a changelog True, a second look seems to indicate that somehow (?) Sphinx is depended on, and on my system Sphinx is reliant on the jinja. I will have to see into details of my Sphinx package. ** OK my Sphinx appears to be have been installed outside of the package manager, I assume through pip. In this case, I am led to assume that this is no longer considered a bug. I believe this is a safe assumption. If I learn the contrary, I will report back. yep, gonna close, thanks |