-
-
Notifications
You must be signed in to change notification settings - Fork 21
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
conda bug prevents installing anything that depends on petsc #147
Labels
Comments
@minrk We need your input here. |
This was referenced Jul 9, 2022
Arg, this is certainly a conda solver bug that it can't merge overlapping globs (conda/conda#11442). The only solution in the meantime is to be consistent with pinning. The above 3 PRs rely on the new run_exports to ensure consistent pinning. |
This was referenced Jul 10, 2022
minrk
changed the title
Problem with conda update with new petsc version
conda bug prevents installing anything that depends on petsc
Jul 12, 2022
This was referenced Jul 12, 2022
repodata patch has been applied, so this should be resolved. |
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Solution to issue cannot be found in the documentation.
Issue
Hi,
a weird issue occurs on my side when updating conda environment today :
After searching a bit, it appears to arise when anaconda is comparing version specifications, and find incompatibility between two build of petsc, namely :
And because
*complex*
is not equal tocomplex_*
, conda crashes 😅After looking a bit at the recent changes, I noticed the change at line 27 in 7c2b211 that may have something to do with it (but I'm not so sure at all, it's just a first hypothesis).
Finally, I could avoid the crash (and perform an update) by forcing conda to merge the two specifications when identifying petsc (hard coded in conda code), but I'm not sure this is a valid and safe way to solve it ...
PS : depending on the conda update (if only one package, ...), the exception can also be :
Installed packages
Environment info
The text was updated successfully, but these errors were encountered: