* python_export() is part of private eclass API. * Please call python_get*() instead. /var/tmp/portage/dev-java/jython-2.7.0-r2/temp/jython: /usr/share/bashdb/bashdb-main.inc: No such file or directory /var/tmp/portage/dev-java/jython-2.7.0-r2/temp/jython: warning: cannot start debugger; debugging mode disabled Traceback (most recent call last): File <string>, line 1, in <module> ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_desktop-20200328-051514 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-9.3.0 * clang version 10.0.0 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/10/bin /usr/lib/llvm/10 10.0.0 Available Python interpreters, in order of preference: [1] python3.8 [2] python3.7 [3] python3.6 [4] python2.7 (fallback) Available Ruby profiles: [1] ruby24 (with Rubygems) [2] ruby25 (with Rubygems) * Available Rust versions: [1] rust-1.42.0 * The following VMs are available for generation-2: *) IcedTea JDK 3.15.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm The Glorious Glasgow Haskell Compilation System, version 8.0.2 timestamp of HEAD at this tinderbox image: /var/db/repos/gentoo Sat 04 Apr 2020 08:37:49 AM UTC emerge -qpvO dev-java/jython [ebuild N ] dev-java/jython-2.7.0-r2 USE="-doc -examples -source -test"
Created attachment 629852 [details] emerge-info.txt
Created attachment 629854 [details] dev-java:jython-2.7.0-r2:20200404-100219.log
Created attachment 629856 [details] emerge-history.txt
Created attachment 629858 [details] environment
Created attachment 629860 [details] etc.portage.tbz2
Created attachment 629862 [details] logs.tbz2
I can confirm this on my machine. seems like it needs app-shells/bashdb but it seems even after manually installing app-shells/bashdb there is an error. will attach both build.log files
Hello if you are looking in the logs you will find this: * python_export() is part of private eclass API. * Please call python_get*() instead. I think the problem is in the file "temp/environment" Only in one line you will find python_export. IN all other lines there is _python_export. I will try if I this is the problem
(In reply to Bernd Martin Wollny from comment #8) > Hello if you are looking in the logs > you will find this: > > * python_export() is part of private eclass API. > * Please call python_get*() instead. > > > I think the problem is in the file "temp/environment" > > Only in one line you will find python_export. > IN all other lines there is _python_export. > > I will try if I this is the problem I have missed two lines... ------------------------------------------------ * python_export() is part of private eclass API. * Please call python_get*() instead. python-exec: EPYTHON value invalid (jython2.7). bad option: `-m' Use -h or --help to see options. ------------------------------------------------ this is the correct error message
Workaround ---------- disable python for dev-java/bsf
*** This bug has been marked as a duplicate of bug 645808 ***
