-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Portage errors when using pypy #11
Comments
It's a technical limitation. Portage has only a single configuration directory that is shared by all Python versions. Once SLR registers itself there, Portage sees it with all Python versions even though not all can support SLR. |
Will not being able to import this set effect functionality? It does not seem to as SLR is still locating and building packages... |
This is caused by |
My "fix" right now is to comment every line in the /usr/share/portage/config/sets/smart-live-rebuild.conf file - you still can't use emerge @smart-live-rebuild obviously, but at least the error is gone |
I use Portage with pypy, as opposed to the usual python3.6/7 package. If I emerge smart-live-rebuild, whenever I use Portage I get the following error message
This can be worked around by eselecting python3.6 as opposed to pypy, but I still think this is a bug.
The text was updated successfully, but these errors were encountered: