-
Notifications
You must be signed in to change notification settings - Fork 2
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
git-annex -m conda installation fails in CI #206
Comments
seems has started recently
googled myself into https://stackoverflow.com/questions/77617946/solve-conda-libmamba-solver-libarchive-so-19-error-after-updating-conda-to-23 which pointed to and boils down to libmamba coming from main archive while the rest from conda-forge. Workarounds are multitude (e.g. adding but if I don't hear back, we might need to add a workaround of some kind (e.g. set to "classic" resolved in our created miniconda env), or add handling of crash/error and providing |
ok, besides adding
and then add all provided, e.g.
I think this way we could then enforce in our CI installation consistent use of conda-forge. |
This is really to see if we would overcome problem with the resolver as reported in datalad/datalad-installer#206
This is really to see if we would overcome problem with the resolver as reported in datalad/datalad-installer#206
Seen in datalad/datalad#7661 (for any runs I didn't cancel fast enough)
The text was updated successfully, but these errors were encountered: