`name=version=build` syntax expands to `name==version=build`, causing `PackageNotFound` errors
jaimergp opened this issue · comments
Comes from #285. Check there for full details.
The gist is that there must be a MatchSpec
bug that causes issues with the roundtrip required to parse and re-write the environment.yaml (to add the Python version, I guess?). This might be related: conda/conda#9980 (comment)
Workflow setup:
name: Tests with conda/mamba
runs-on: ${{ matrix.os }}
strategy:
fail-fast: false
matrix:
os: ["ubuntu-latest", "macos-latest", "windows-latest"]
steps:
- uses: actions/checkout@v3
- uses: conda-incubator/setup-miniconda@v2
with:
python-version: "3.10"
mamba-version: "*"
channels: conda-forge,defaults
channel-priority: true
environment-file: ./environment_locked_py310.yml
My environment_locked_py310.yml
name: dymoval_dev
channels:
- conda-forge
- defaults
dependencies:
- alabaster=0.7.13=pyhd8ed1ab_0
- apeye=1.3.0=pyhd8ed1ab_0
- apeye-core=1.1.2=pyhd8ed1ab_0
- autodocsumm=0.2.11=pyhd8ed1ab_0
- babel=2.12.1=pyhd8ed1ab_1
- beautifulsoup4=4.12.2=pyha770c72_0
- black=23.3.0=py310hbe9552e_1
- brotli=1.0.9=h1a8c8d9_8
- brotli-bin=1.0.9=h1a8c8d9_8
- brotlipy=0.7.0=py310h8e9501a_1005
- bzip2=1.0.8=h3422bc3_4
...
- xorg-libxau=1.0.9=h27ca646_0
- xorg-libxdmcp=1.1.3=h27ca646_0
- xz=5.2.6=h57fd34a_0
- yaml=0.2.5=h3422bc3_2
- zipp=3.15.0=pyhd8ed1ab_0
- zstd=1.5.2=hf913c23_6
The error from github actions:
/usr/share/miniconda/condabin/conda env update --name test --file /home/runner/work/dymoval/dymoval/setup-miniconda-patched-environment_locked_py310.yml
Collecting package metadata (repodata.json): ...working... done
Solving environment: ...working... failed
Warning:
ResolvePackageNotFound:
- tk==8.6.12=he1e0b03_0
- lcms2==2.15=hd835a16_1
- libaec==1.0.6=hb7217d7_1
...
Error: The process '/usr/share/miniconda/condabin/conda' failed with exit code 1
Notice the double equals ==
in the error message.