I tried to install jsoncpp in a bare stage3, and it fails with this: Traceback (most recent call last): File "/usr/lib/python-exec/python3.6/meson", line 6, in <module> from pkg_resources import load_entry_point ModuleNotFoundError: No module named 'pkg_resources' It's trying to use python3.6 which isn't enabled in the setuptools package, but it doesn't look like jsoncpp has USE flags to disable that version. Reproducible: Always Steps to Reproduce: 1. emerge -v dev-libs/jsoncpp Actual Results: Configure fails. Expected Results: It should build and install. It works after installing dev-python/setuptools with python3_6 enabled.
Bugzilla is throwing server errors when I try to attach build.log, so I'll just paste it: * Package: dev-libs/jsoncpp-1.9.3_pre20200412 * Repository: gentoo * Maintainer: mgorny@gentoo.org * USE: abi_x86_64 amd64 elibc_glibc kernel_linux userland_GNU * FEATURES: preserve-libs sandbox userpriv usersandbox * Using python3.6 to build >>> Unpacking source... >>> Unpacking jsoncpp-1.9.3_pre20200412.tar.gz to /var/tmp/portage/dev-libs/jsoncpp-1.9.3_pre20200412/work >>> Source unpacked in /var/tmp/portage/dev-libs/jsoncpp-1.9.3_pre20200412/work >>> Preparing source in /var/tmp/portage/dev-libs/jsoncpp-1.9.3_pre20200412/work/jsoncpp-90ca694e4697497a8c2bc8c60a9c9f89e7290a10 ... >>> Source prepared. >>> Configuring source in /var/tmp/portage/dev-libs/jsoncpp-1.9.3_pre20200412/work/jsoncpp-90ca694e4697497a8c2bc8c60a9c9f89e7290a10 ... Traceback (most recent call last): File "/usr/lib/python-exec/python3.6/meson", line 6, in <module> from pkg_resources import load_entry_point ModuleNotFoundError: No module named 'pkg_resources' * ERROR: dev-libs/jsoncpp-1.9.3_pre20200412::gentoo failed (configure phase): * __eapi7_ver_compare: invalid version: * * Call stack: * ebuild.sh, line 125: Called src_configure * environment, line 2293: Called meson_src_configure * environment, line 1517: Called ver_test '' '-lt' '0.54' * environment, line 3022: Called __eapi7_ver_compare '' '0.54' * environment, line 217: Called die * The specific snippet of code: * [[ ${va} =~ ${re} ]] || die "${FUNCNAME}: invalid version: ${va}"; * * If you need support, post the output of `emerge --info '=dev-libs/jsoncpp-1.9.3_pre20200412::gentoo'`, * the complete build log and the output of `emerge -pqv '=dev-libs/jsoncpp-1.9.3_pre20200412::gentoo'`. * The complete build log is located at '/var/tmp/portage/dev-libs/jsoncpp-1.9.3_pre20200412/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-libs/jsoncpp-1.9.3_pre20200412/temp/environment'. * Working directory: '/var/tmp/portage/dev-libs/jsoncpp-1.9.3_pre20200412/work/jsoncpp-90ca694e4697497a8c2bc8c60a9c9f89e7290a10' * S: '/var/tmp/portage/dev-libs/jsoncpp-1.9.3_pre20200412/work/jsoncpp-90ca694e4697497a8c2bc8c60a9c9f89e7290a10'
Please run 'eselect python cleanup' and try again. Likely a local configuration problem
Now the stage3s have been wiped out from all the mirrors I checked, so I can't try again. The problem occurred in https://mirror.sjc02.svwh.net/gentoo/releases/amd64/autobuilds/20200422T214502Z/hardened/stage3-amd64-hardened+nomultilib-20200422T214502Z.tar.xz with no relevant configuration changes.
Okay, stage3s are back, so I can look at this again. It breaks when updating with --changed-use because of the Python version switch. The setuptools package is rebuilt before meson, and meson-using packages (several in addition to this one) are rebuilt between them, which are all broken. I guess I just have to wait for new stage3s to be built with Python 3.7 and revert the switch until then.
I think this is no dev-libs/jsoncpp bug, but a problem with your stage3. The situation seems to be a bit more complicate and requires some analysis. We can not help you efficiently via bug tracker. The bug tracker aims rather on specific problems in .ebuilds and less on individual systems. I have had very good experience on the gentoo IRC [1] with questions like this. Of course there are also forums and mailing lists [2,3]. I hope you understand, that I will close the bug here therefore and wish you good luck on one of the mentioned channels [4]. Please reopen the ticket in order to provide an indication for an specific error in an ebuild or any gentoo related product. [1] https://www.gentoo.org/get-involved/irc-channels/ [2] https://forums.gentoo.org/ [3] https://www.gentoo.org/get-involved/mailing-lists/all-lists.html [4] https://www.gentoo.org/support/
