Closed orion160 closed 2 months ago
I am also running into this issue
Yeah, this was brought to my attention last week. I have a colleague who got it working again; I'll ask him to post a fix.
I worked around this issue by tweaking the environment.$$$.yml file directly to remove the clashing duplicates. If you open environment.icXLm0.yml, you should see dups for zlib and libzlib. If you remove the dups so that you are only left with the newer of the two versions, you should then be able to rerun this command and complete the Sparta environment setup:
/home/cc/miniconda3/bin/conda env create -f=environment.icXLm0.yml -n sparta
Curious, what version of conda
did you guys use? I just tied it with conda 24.7.1 with no issues...
One item to note is the conda feedstock is tied to CI rendered from conda smithy
. I have a PR to try to get this working again (and might also fix the conda environment setup). PR #510
Welp, I slept on it and tried again this morning and have NEW errors. Something's borked for sure. Thinking about supplying a fixed environment file that everyone can use (and update it every now and then).
I narrowed it down to conda smithy
insisting to move us to boost 1.85, which has dependencies on newer libraries which are in conflict with older libraries in the same rendering. I'm trying to get the renderer to include boost 1.78, but it's gleefully ignored -- in fact, BOTH 1.78 and 1.85 are trying to be installed. I have no idea which environment/library is insisting on installing it.
I manually removed boost 1.85 from the rendered environment file and had 100% success in package resolution as well as a clean sparta build. :man_shrugging:
@timsnyder do you know how to force the render to NOT include a specific package?
For now, I've created a safe environment for render: https://github.com/sparcians/map/blob/master/scripts/rendered_safe_environment.yaml and updated the main README (step 5) to use it.