Summary: | python-exec: Invalid impl in /etc/python-exec/python-exec.conf: python3.3 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Martin Mokrejš <mmokrejs> |
Component: | Current packages | Assignee: | Python Gentoo Team <python> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | mgorny |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Martin Mokrejš
2017-04-10 10:02:13 UTC
It happened to me on another host just now. Here is the causing package: >>> Installing (1 of 8) dev-lang/python-exec-2.4.4::gentoo * This package will overwrite one or more files that may belong to other * packages (see list below). You can use a command such as `portageq * owners / <filename>` to identify the installed package that owns a * file. If portageq reports that only one package owns a file then do * NOT file a bug report. A bug report is only useful if it identifies at * least two or more packages that are known to install the same file(s). * If a collision occurs and you can not explain where the file came from * then you should simply ignore the collision since there is not enough * information to determine if a real problem exists. Please do NOT file * a bug report at http://bugs.gentoo.org unless you report exactly which * two packages install the same file(s). See * http://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how to * solve the problem. And once again, please do NOT file a bug report * unless you have completely understood the above message. * * Detected file collision(s): * * /usr/bin/python2 * /usr/bin/python3 * /usr/bin/python-config * /usr/bin/2to3 * /usr/bin/python * /usr/bin/pydoc * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * None of the installed packages claim the file(s). * * Package 'dev-lang/python-exec-2.4.4' merged despite file collisions. * If necessary, refer to your elog messages for the whole content of the * above message. * You seem to have just upgraded into the new version of python-exec * that uses python-exec.conf for configuration. The ebuild has attempted * to convert your previous configuration to the new format, resulting * in the following preferences (most preferred version first): * * python2.7 * python3.4 * * Those interpreters will be preferred when running Python scripts or * calling wrapped Python executables (python, python2, pydoc...). * If none of the preferred interpreters are supported, python-exec will * fall back to the newest supported Python version. * * Please note that due to the ambiguous character of the old settings, * you may want to modify the preference list yourself. In order to do so, * open the following file in your favorite editor: * * /etc/python-exec/python-exec.conf * * For more information on the new configuration format, please read * the comment on top of the installed configuration file. Yeah, I just dropped the 3.3 from the /etc/python-exec/python-exec.conf file. (In reply to Martin Mokrejš from comment #0) > Hi, > on some older installation I started to get the following after some > updates: > > python-exec: Invalid impl in /etc/python-exec/python-exec.conf: python3.3 Which means you've got very old Python enabled in configuration. It's merely a warning. > It is printed out at several emerge steps, also here with a more useful > message: > > # python-updater > python-exec: Invalid impl in /etc/python-exec/python-exec.conf: python3.3 > python-exec: Invalid impl in /etc/python-exec/python-exec.conf: python3.3 > python-exec: Invalid impl in /etc/python-exec/python-exec.conf: python3.3 > * '/usr/bin/python2' is not valid symlink This only indicates python-updater is completely broken and useless. You aren't supposed to run it. By your next comment, I presume you've already figured out how to use the config file. |