https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: dev-python/Babel-2.10.2 fails to compile. Discovered on: amd64 (internal ref: ci)
Created attachment 785435 [details] build.log build log and emerge --info
* Checking whether python3_11 is suitable ... * >=dev-lang/python-3.11.0_beta1-r1:3.11[threads(+)] ... [ ok ] * python_check_deps ... [ ok ] * Using python3.11 in global scope * python3_11: running distutils-r1_run_phase python_configure_all Traceback (most recent call last): File "/var/tmp/portage/dev-python/Babel-2.10.2/work/Babel-2.10.2/scripts/import_cldr.py", line 35, in <module> from babel import dates, numbers ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/var/tmp/portage/dev-python/Babel-2.10.2/work/Babel-2.10.2/babel/dates.py", line 21, in <module> import pytz as _pytz ^^^^^^^^^^^^^^^^^^^^ ModuleNotFoundError: No module named 'pytz'
eselect python list Available Python interpreters, in order of preference: [1] python3.10 [2] python3.11 (fallback) Shouldn't the build be using the default Python interpreter instead of the fallback (3.11 beta)?
(In reply to Chris Smith from comment #3) > eselect python list > Available Python interpreters, in order of preference: > [1] python3.10 > [2] python3.11 (fallback) > > Shouldn't the build be using the default Python interpreter instead of the > fallback (3.11 beta)? No, python-any-r1 allows using the latest available interpreter as long as the deps are satisfied.
(In reply to Sam James from comment #4) > (In reply to Chris Smith from comment #3) > > eselect python list > > Available Python interpreters, in order of preference: > > [1] python3.10 > > [2] python3.11 (fallback) > > > > Shouldn't the build be using the default Python interpreter instead of the > > fallback (3.11 beta)? > > No, python-any-r1 allows using the latest available interpreter as long as > the deps are satisfied. ... although not sure I get what's happening here? ago does not have python_targets_python3_11 and it's distutils-r1. And the dep exists.
sorry, I get it now, I was looking at the wrong ebuild.
No python_targets_python3_11 here. */* PYTHON_TARGETS: -* python3_10 */* PYTHON_SINGLE_TARGET: -* python3_10
(In reply to Chris Smith from comment #7) > No python_targets_python3_11 here. > > */* PYTHON_TARGETS: -* python3_10 > */* PYTHON_SINGLE_TARGET: -* python3_10 yeah, sorry, I get it now, it's python-any-r1 ish related still for global scope usage, but need to fix dep for pytz for the generator bit
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b4a0cb7cd36db1d75416c2d4e5da8c4d97f98a96 commit b4a0cb7cd36db1d75416c2d4e5da8c4d97f98a96 Author: Sam James <sam@gentoo.org> AuthorDate: 2022-06-15 13:58:45 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2022-06-15 13:58:52 +0000 dev-python/Babel: fix import_cldr.py deps Closes: https://bugs.gentoo.org/852158 Signed-off-by: Sam James <sam@gentoo.org> dev-python/Babel/Babel-2.10.2.ebuild | 2 ++ 1 file changed, 2 insertions(+)
This is still not working for me, same error. My /etc/python-exec/python-exec.conf contains only "python3.9" and pitz is only compiled for this version. Still Babel-2.10.2 is trying to use python3.11
will poke more in mo
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=fbb8e48c4b62c81f6edb66662244ddc818c3cb68 commit fbb8e48c4b62c81f6edb66662244ddc818c3cb68 Author: Sam James <sam@gentoo.org> AuthorDate: 2022-06-15 14:54:53 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2022-06-15 14:55:05 +0000 dev-python/Babel: finish off pytz fix Closes: https://bugs.gentoo.org/852158 Signed-off-by: Sam James <sam@gentoo.org> dev-python/Babel/Babel-2.10.2.ebuild | 8 ++++++++ 1 file changed, 8 insertions(+)
*** Bug 852185 has been marked as a duplicate of this bug. ***
