-
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
Commit conda-lock.yml to repository #122
Comments
Maybe time for me to pick up on #14 again 😆 Do we want both the |
Oh wait actually, #14 might have been chewing on too much as it was trying to install from the |
Yeah for starters just linux-64
Looks like other platforms aren't happy with a few of the packages:
|
Syncing with the changes at ICESAT-2HackWeek/website-2024#18 by: - Pinning `sphinx` explicity to 7.3 (was resolving to 5.1.1 before) - Upgrade `awscli` from 1.27.76 to 2.17 to resolve conflict on `docutils` (see ICESAT-2HackWeek/website-2024#18 (comment)) - Downgrade `ipython` from 8.20.0 to 8.17 to resolve conflict on `prompt_toolkit` (see ICESAT-2HackWeek/website-2024#18 (comment)) This PR also adds a 'conda-lock.yml' (following #122) in addition to the existing 'conda-lock-linux64.yml' file.
It would be useful to commit the unified lockfile to this repository in addition to the platform-specific
https://github.com/CryoInTheCloud/hub-image/blob/main/conda-linux-64.lock
This would facilitate installing the cryocloud environment (at least the conda-forge part) on different systems
ICESAT-2HackWeek/website-2024#17 (comment)
The text was updated successfully, but these errors were encountered: