return next(matches).load() StopIteration Error: '/usr/bin/sip5 -V' did not generate any output. * ERROR: dev-python/qscintilla-python-2.11.6::gentoo failed (configure phase): * (no error message) * * Call stack: ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_desktop_systemd-j3-20210610-203140 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-11.1.0 * clang version 12.0.0 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/12/bin /usr/lib/llvm/12 12.0.0 Python 3.9.5 Available Ruby profiles: [1] ruby26 (with Rubygems) [2] ruby30 (with Rubygems) * Available Rust versions: [1] rust-bin-1.52.1 * The following VMs are available for generation-2: 1) IcedTea JDK 3.16.0 [icedtea-bin-8] *) AdoptOpenJDK 8.292_p10 [openjdk-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 [2] openjdk-bin-8 system-vm The Glorious Glasgow Haskell Compilation System, version 8.10.4 [1] php7.3 * [2] php7.4 [3] php8.0 HEAD of ::gentoo commit 86d0760439fe4376c811d1583c5cee816c11fdd6 Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Tue Jun 15 18:50:09 2021 +0000 2021-06-15 18:50:08 UTC emerge -qpvO dev-python/qscintilla-python [ebuild N ] dev-python/qscintilla-python-2.11.6 USE="-debug" PYTHON_TARGETS="python3_9 -python3_8"
Created attachment 716346 [details] emerge-info.txt
Created attachment 716349 [details] dev-python:qscintilla-python-2.11.6:20210615-192817.log
Created attachment 716352 [details] emerge-history.txt
Created attachment 716355 [details] environment
Created attachment 716358 [details] etc.portage.tar.bz2
I cannot reproduce but it seems to be a problem with the dev-python/sip installation. Can you please try `sip5 -V` on its own in a terminal and see what it prints?
(In reply to Davide Pesavento from comment #6) > I cannot reproduce but it seems to be a problem with the dev-python/sip > installation. > > Can you please try `sip5 -V` on its own in a terminal and see what it prints? 17_1_desktop_systemd-j3-20210610-203140 /var/tmp/tb # sip5 -V Traceback (most recent call last): File "/usr/lib/python-exec/python3.9/sip5", line 33, in <module> sys.exit(load_entry_point('sip==5.5.0', 'console_scripts', 'sip5')()) File "/usr/lib/python-exec/python3.9/sip5", line 25, in importlib_load_entry_point return next(matches).load() StopIteration
I'm not sure what's going on. The error comes from the wrapper script. python@, any ideas?
I'm encountering this issue when building dev-python/PyQt5, but I can also reproduce it in a normal shell. This issue appears to occur due to having multiple slots of dev-python/sip installed. There's a debian bug about it noting: "Stop installing the .dist-info directory. It causes a name conflict with SIP 5." from https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976983 The issue is fixed for me after depcleaning dev-python/sip to remove the old slot.
(In reply to telans from comment #9) > There's a debian bug about it noting: "Stop installing the .dist-info > directory. It causes a name conflict with SIP 5." from > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976983 Thanks. I suppose we can adopt the same workaround.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3b5cdd5604f885c8b0b68be0dc00fddaa5cfe8ac commit 3b5cdd5604f885c8b0b68be0dc00fddaa5cfe8ac Author: Davide Pesavento <pesa@gentoo.org> AuthorDate: 2021-06-19 19:37:06 +0000 Commit: Davide Pesavento <pesa@gentoo.org> CommitDate: 2021-06-19 19:37:06 +0000 dev-python/sip: stop installing .dist-info Closes: https://bugs.gentoo.org/796251 Package-Manager: Portage-3.0.20, Repoman-3.0.3 Signed-off-by: Davide Pesavento <pesa@gentoo.org> dev-python/sip/sip-4.19.25-r1.ebuild | 93 ++++++++++++++++++++++ .../{sip-5.5.0-r1.ebuild => sip-5.5.0-r2.ebuild} | 3 +- dev-python/sip/sip-6.1.1.ebuild | 3 +- 3 files changed, 97 insertions(+), 2 deletions(-)
*** Bug 796923 has been marked as a duplicate of this bug. ***
*** Bug 802456 has been marked as a duplicate of this bug. ***
