-
Notifications
You must be signed in to change notification settings - Fork 382
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
With latest conda-forge repodata, install both boost and gazebo results in pypy being installed, differently from conda #986
Comments
@traversaro is this a fresh environment with latest libsolv (0.7.19)? I pushed an update to libsolv on Friday which should have resolved this issue. Would be interesting to hear which libsolv version you have. |
For reference, these two PRs are included in the latest libsolv on conda-forge: |
I was in an hurry when I opened the issue. I am currently in the fields, as soon as I back at the laptop I will provide the full details on the base env. |
Thanks, no worries! |
Yes, it seems that the latest libsolv is used:
|
Interestingly, a regular Python 3.8 is installed if the installation command is:
|
FYI I pinned conda-forge's libsolv to 0.7.18 and the issue does not appear, so it seems to be a regression in conda-forge's libsolv 0.7.19 (possibly related to https://github.com/conda-forge/libsolv-feedstock/pull/49/files ?), see robotology/robotology-superbuild#788 . |
Note that it is also possible that the fact that a non-PyPy Python was installed was never explicitly intentional, and in this case we were a victim of Hyrum's Law. |
@traversaro thanks for letting me know! PyPy comes with a |
thanks @traversaro this issue is currently "fixed" by removing the libsolv package that gave us trouble. I am planning to upload a new one with a new patch that should work better and I tested this specific case with boost + gazebo in the development: openSUSE/libsolv#457 I am thinking about rolling it out today 🤞 |
Thanks @wolfv, indeed in robotology/robotology-superbuild#833 we removed the pinnings and everything is working fine for now. |
With the latest conda-forge data, mamba and conda are giving a different resolution when trying to install both boost and gazebo. In particular, mamba tries to install pypy, that typically it is not a great choice as default Python unless the user explicitly asked for it.
The text was updated successfully, but these errors were encountered: