Update Initial-Repo-Setup.rst to force conda-lock version

[rohanku]

Related PRs / Issues:

Fixes #1488

Type of change:

• Bug fix
• New feature
• Other enhancement

Impact:

• RTL change
• Software change (RISC-V software)
• Build system change
• Other

Contributor Checklist:

• Did you set main as the base branch?
• Is this PR's title suitable for inclusion in the changelog and have you added a changelog:<topic> label?
• Did you state the type-of-change/impact?
• Did you delete any extraneous prints/debugging code?
• Did you mark the PR with a changelog: label?
• (If applicable) Did you update the conda .conda-lock.yml file if you updated the conda requirements file?
• (If applicable) Did you add documentation for the feature?
• (If applicable) Did you add a test demonstrating the PR?

• (If applicable) Did you mark the PR as Please Backport?

[abejgonzalez]

Do you see your issue with any conda-lock version greater than 0.*? We use the following for our environment which is a bit more flexible.

chipyard/conda-reqs/chipyard.yaml

Line 96 in 0b07958

- conda-lock>=1

I would change it to that to make it more flexible.

[rohanku]

I could do conda-lock=1, since conda-lock>=1 no longer works (version 2.0.0 is the one that is causing issues).

[abejgonzalez]

I could do conda-lock=1, since conda-lock>=1 no longer works (version 2.0.0 is the one that is causing issues).

Lets do that then (if you can also update the lockfiles by changing chipyard/conda-reqs/chipyard.yaml and running: https://github.com/ucb-bar/chipyard/blob/main/scripts/generate-conda-lockfiles.sh that would be great as well). Thanks.

[abejgonzalez]

Update: I'll do this quickly in another PR (since this PR is from a fork).

[rohanku]

Sorry I didn't get around to it, but that would be great. I don't actually have conda on my computer anymore since I decided to install the dependencies I needed manually.