Summary: | sys-apps/razercfg-0.26 - No supported Python implementation in PYTHON_SINGLE_TARGET. | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Anton Bolshakov <anton.bugs> |
Component: | [OLD] Core system | Assignee: | No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it <maintainer-needed> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | peter.karasinski |
Priority: | Normal | ||
Version: | 10.1 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Anton Bolshakov
2014-07-07 07:35:28 UTC
I need to explain my point. While I understand that I have to add python3.3 to the single target list, I was wondering why it is not set by default. My default settings are: PYTHON_SINGLE_TARGET="python3_3" PYTHON_TARGETS="python2_7 python3_3" That's the reason why I can't emerge razercfg package by default After changing single target, I'm facing a problem with libreoffice now: The following REQUIRED_USE flag constraints are unsatisfied: exactly-one-of ( python_single_target_python2_7 python_single_target_python3_3 python_single_target_python3_4 ) .. What about using a per package entry: In /etc/portage/package.use/misc (or similar): sys-apps/razercfg python_single_target_python3_3 My whole system is still set to python 2.7. With this entry it only affects one package. So better than /etc/make.conf perfect, I didn't know that it is possible to specify system use flags in package.use directory Hhm, I do have a minimal ~amd64 chroot, where emerging sys-apps/razercfg-0.30 failed too with * No Python implementation selected for the build. Please set * the PYTHON_SINGLE_TARGET variable in your make.conf to one * of the following values: * * python3_2 python3_3 and I'd really thin, that in such a case it should work w/o suer interaction, or ? This problem is still present in 0.31 and every other package defaults to python3_3 without explicitly setting PYTHON_SINGLE_TARGET, but razercfg fails to emerge. *** This bug has been marked as a duplicate of bug 472932 *** |