I have successful emerged qt:3 and now i wanna emerge knoda from kde-sunset ,
but emerge knoda breaks by dev-db/hk_classes-0.8.3-r1.
Is it bug or i do smth wrong ?
If it is bug, is patch available ?
Or can somebody step by step explain how to fix it and emerge hk_classes-0.8.3-r1 ?
Tnx in advance.
eselect python set 1
python-updater
...
eselect python list
Available Python interpreters:
[1] python2.6 *
[2] python3.1
Below is output from emerge -avN knoda and
emerge --info =dev-db/hk_classes-0.8.3-r1
emerge --info =dev-db/hk_classes-
These are the packages that would be merged, in order:
Total: 9 packages (7 new, 2 in new slots), Size of downloads: 0 kB
Portage tree and overlays:
[0] /usr/portage
[1] /var/lib/layman/kde-sunset
Would you like to merge these packages? [Yes/No]
>>> Verifying ebuild manifests
>>> Starting parallel fetch
>>> Emerging (1 of 9) dev-db/hk_classes-0.8.3-r1 from kde-sunset
* hk_classes-0.8.3.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ]
* xbsql-hk_classes-0.13.tar.gz RMD160 SHA1 SHA256 size ;-) ... [ ok ]
* Package: dev-db/hk_classes-0.8.3-r1
* Repository: kde-sunset
* Maintainer: kde@gentoo.org
* USE: elibc_glibc kernel_linux mysql userland_GNU x86
>>> Unpacking source...
>>> Unpacking hk_classes-0.8.3.tar.bz2 to /var/tmp/portage/dev-db/hk_classes-0.8.3-r1/work
>>> Unpacking xbsql-hk_classes-0.13.tar.gz to /var/tmp/portage/dev-db/hk_classes-0.8.3-r1/work
* Applying hk_classes-0.8.3-gcc43.patch ... [ ok ]
* Running eautoreconf in '/var/tmp/portage/dev-db/hk_classes-0.8.3-r1/work/hk_classes-0.8.3' ...
* Running aclocal ... [ ok ]
* Running libtoolize --copy --force --install --automake ... [ ok ]
* Running aclocal ... [ ok ]
* Running autoconf ... [ ok ]
* Running autoheader ... [ ok ]
* Running automake --add-missing --copy ... [ ok ]
* Running elibtoolize in: hk_classes-0.8.3/
* Applying portage-2.2.patch ...
* Applying sed-1.5.6.patch ...
* Applying as-needed-2.2.6.patch ...
>>> Source unpacked in /var/tmp/portage/dev-db/hk_classes-0.8.3-r1/work
>>> Compiling source in /var/tmp/portage/dev-db/hk_classes-0.8.3-r1/work/hk_classes-0.8.3 ...
* Use PYTHON() instead of python variable. Use python_get_*() instead of PYVER* variables.
* ERROR: dev-db/hk_classes-0.8.3-r1 failed:
* python_version() is banned
*
* Call stack:
* ebuild.sh, line 56: Called src_compile
* environment, line 5138: Called python_version
* environment, line 5086: Called die
* The specific snippet of code:
* die "${FUNCNAME}() is banned"
*
* If you need support, post the output of 'emerge --info =dev-db/hk_classes-0.8.3-r1',
* the complete build log and the output of 'emerge -pqv =dev-db/hk_classes-0.8.3-r1'.
* This ebuild is from an overlay named 'kde-sunset': '/var/lib/layman/kde-sunset/'
* The complete build log is located at '/var/tmp/portage/dev-db/hk_classes-0.8.3-r1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-db/hk_classes-0.8.3-r1/temp/environment'.
* S: '/var/tmp/portage/dev-db/hk_classes-0.8.3-r1/work/hk_classes-0.8.3'
>>> Failed to emerge dev-db/hk_classes-0.8.3-r1, Log file:
* Messages for package dev-db/hk_classes-0.8.3-r1:
* Use PYTHON() instead of python variable. Use python_get_*() instead of PYVER* variables.
* ERROR: dev-db/hk_classes-0.8.3-r1 failed:
* python_version() is banned
*
* Call stack:
* ebuild.sh, line 56: Called src_compile
* environment, line 5138: Called python_version
* environment, line 5086: Called die
* The specific snippet of code:
* die "${FUNCNAME}() is banned"
*
* If you need support, post the output of 'emerge --info =dev-db/hk_classes-0.8.3-r1',
* the complete build log and the output of 'emerge -pqv =dev-db/hk_classes-0.8.3-r1'.
* This ebuild is from an overlay named 'kde-sunset': '/var/lib/layman/kde-sunset/'
* The complete build log is located at '/var/tmp/portage/dev-db/hk_classes-0.8.3-r1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-db/hk_classes-0.8.3-r1/temp/environment'.
* S: '/var/tmp/portage/dev-db/hk_classes-0.8.3-r1/work/hk_classes-0.8.3'
dev-db/hk_classes-0.8.3-r1
