conda install -n base conda-lock no longer works with existing Lockfiles due to new conda-lock release

[rohanku]

Background Work

• Yes, I searched the mailing list
• Yes, I searched prior issues
• Yes, I searched the documentation

Chipyard Version and Hash

Release: 1.5.0
Hash: a6a6a6

OS Setup

Darwin rohanmbp.local 22.4.0 Darwin Kernel Version 22.4.0: Mon Mar 6 21:00:17 PST 2023; root:xnu-8796.101.5~3/RELEASE_X86_64 x86_64

conda-lock version 2.0.0

Other Setup

Followed documentation for setting up Chipyard repository.

Current Behavior

conda-lock is unable to read Lockfiles during ./build-setup.sh

Expected Behavior

conda-lock should be able to parse Lockfiles (works when constrained to version 1.4.0 using conda install -n base conda-lock=1.4.0)

Other Information

No response

[jerryz123]

Are you saying that the amending the instructions to be conda install -n base conda-lock=1.4.0 (forcing a version) will fix the issue? If so, can you just PR it to main?

[JL102]

Are you saying that the amending the instructions to be conda install -n base conda-lock=1.4.0 (forcing a version) will fix the issue? If so, can you just PR it to main?

I can verify that downgrading conda-lock from v2.0.0 to v1.4.0 stops the issue as described on this separate forum thread: https://discuss.python.org/t/validation-error/27335
The issue I was encountering was not during the conda install -n base conda-lock step, but in fact occurred when attempting to run build-setup.sh.

[fangrouli]

I can verify that downgrading conda-lock from v2.0.0 to v1.4.0 stops the issue as described
in fact occurred when attempting to run build-setup.sh.

Exactly same behaviour. Recommends quoting this in the documentation.

[jspkay]

I had the same issue and confirm that downgrading conda-lock to 1.4.0 solved the problem