proof: https://bpaste.net/show/b965e2164642 After one-shot installing dev-python/jinja, pbr-1.9.1 installed successfully bpaste contents just incase: ---- * Package: dev-python/pbr-1.9.1 * Repository: gentoo * Maintainer: prometheanfire@gentoo.org openstack@gentoo.org * USE: abi_x86_64 amd64 elibc_glibc kernel_linux python_targets_python2_7 python_targets_python3_4 userland_GNU * FEATURES: preserve-libs sandbox userpriv usersandbox >>> Unpacking source... >>> Unpacking pbr-1.9.1.tar.gz to /var/tmp/portage/dev-python/pbr-1.9.1/work >>> Source unpacked in /var/tmp/portage/dev-python/pbr-1.9.1/work >>> Preparing source in /var/tmp/portage/dev-python/pbr-1.9.1/work/pbr-1.9.1 ... * rogue tests disabled >>> Source prepared. >>> Configuring source in /var/tmp/portage/dev-python/pbr-1.9.1/work/pbr-1.9.1 ... >>> Source configured. >>> Compiling source in /var/tmp/portage/dev-python/pbr-1.9.1/work/pbr-1.9.1 ... * python2_7: running distutils-r1_run_phase distutils-r1_python_compile /usr/bin/python2.7 setup.py build Traceback (most recent call last): File "setup.py", line 22, in <module> **util.cfg_to_args()) File "/var/tmp/portage/dev-python/pbr-1.9.1/work/pbr-1.9.1/pbr/util.py", line 264, in cfg_to_args wrap_commands(kwargs) File "/var/tmp/portage/dev-python/pbr-1.9.1/work/pbr-1.9.1/pbr/util.py", line 566, in wrap_commands cmdclass = ep.resolve() File "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py", line 2361, in resolve module = __import__(self.module_name, fromlist=['__name__'], level=0) File "/usr/lib64/python2.7/site-packages/sphinx/setup_command.py", line 23, in <module> from sphinx.application import Sphinx File "/usr/lib64/python2.7/site-packages/sphinx/application.py", line 31, in <module> from sphinx.roles import XRefRole File "/usr/lib64/python2.7/site-packages/sphinx/roles.py", line 21, in <module> from sphinx.util import ws_re File "/usr/lib64/python2.7/site-packages/sphinx/util/__init__.py", line 29, in <module> import jinja2 ImportError: No module named jinja2 * ERROR: dev-python/pbr-1.9.1::gentoo failed (compile phase): * (no error message) * * Call stack: * ebuild.sh, line 133: Called src_compile * environment, line 3659: Called distutils-r1_src_compile * environment, line 942: Called _distutils-r1_run_foreach_impl 'distutils-r1_python_compile' * environment, line 347: Called python_foreach_impl 'distutils-r1_run_phase' 'distutils-r1_python_compile' * environment, line 3182: Called multibuild_foreach_variant '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'distutils-r1_python_compile' * environment, line 2291: Called _multibuild_run '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'distutils-r1_python_compile' * environment, line 2289: Called _python_multibuild_wrapper 'distutils-r1_run_phase' 'distutils-r1_python_compile' * environment, line 609: Called distutils-r1_run_phase 'distutils-r1_python_compile' * environment, line 933: Called distutils-r1_python_compile * environment, line 808: Called esetup.py 'build' * environment, line 1435: Called die * The specific snippet of code: * "${@}" || die "${die_args[@]}"; * * If you need support, post the output of `emerge --info '=dev-python/pbr-1.9.1::gentoo'`, * the complete build log and the output of `emerge -pqv '=dev-python/pbr-1.9.1::gentoo'`. * The complete build log is located at '/var/tmp/portage/dev-python/pbr-1.9.1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-python/pbr-1.9.1/temp/environment'. * Working directory: '/var/tmp/portage/dev-python/pbr-1.9.1/work/pbr-1.9.1' * S: '/var/tmp/portage/dev-python/pbr-1.9.1/work/pbr-1.9.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
(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
