* python3_2: running distutils-r1_run_phase python_compile_all RefactoringTool: Skipping implicit fixer: buffer RefactoringTool: Skipping implicit fixer: idioms RefactoringTool: Skipping implicit fixer: set_literal RefactoringTool: Skipping implicit fixer: ws_comma RefactoringTool: Refactored jinjaext.py RefactoringTool: Files that were modified: RefactoringTool: jinjaext.py make -j8 html sphinx-build -b html -d _build/doctrees . _build/html Traceback (most recent call last): File "/usr/bin/sphinx-build-python3.2", line 5, in <module> from pkg_resources import load_entry_point File "/usr/lib64/python3.2/site-packages/pkg_resources.py", line 2823, in <module> working_set.require(__requires__) File "/usr/lib64/python3.2/site-packages/pkg_resources.py", line 697, in require needed = self.resolve(parse_requirements(requirements)) File "/usr/lib64/python3.2/site-packages/pkg_resources.py", line 595, in resolve raise DistributionNotFound(req) pkg_resources.DistributionNotFound: Jinja2>=2.3 make: *** [html] Error 1 * ERROR: dev-python/jinja-2.6-r100 failed (compile phase): * emake failed dev-python/sphinx-1.1.3-r7
Same here. 'USE=-doc emerge -v1 =dev-python/jinja-2.6-r100' works.
jinja needs to be installed to build its own docs using sphinx. If you install dev-python/jinja[-doc]:compat first, and then remerge it with doc enabled, it will work fine. On a fresh install this would be blocked by a circular dep between sphinx and jinja. I'm not sure how we can enforce this here.
I suspect it is only a problem if you had upgraded to jinja-2.7 before I added the jinja-2.6-r100 ebuild to the tree.
Yeah, it's an issue with the installation order. The only way around it would be to have portage build both jinja-2.6-r100 and jinja-2.7 before unmerging jinja-2.6-r2, but I don't see a way to make it do that. If someone can come up with a set of dependencies that would cause portage to throw an error during dep resolution, that would also be acceptable.
(In reply to comment #2) > jinja needs to be installed to build its own docs using sphinx. If you > install dev-python/jinja[-doc]:compat first, and then remerge it with doc > enabled, it will work fine. Worked for me.
I guess another possibility would be to drop the doc use flag on the compat slot.
This version of jinja is no longer in the tree and I see no indication that the new version suffers from this issue. Is it alright if we close this as invalid at this point? If I don't hear anything by Sept 13, I'll mark this as invalid.
