The process '/usr/share/miniconda/condabin/conda' failed with exit code 1

The process '/usr/share/miniconda/condabin/conda' failed with exit code 1

The process '/usr/share/miniconda/condabin/conda' failed with exit code 1

The process '/usr/share/miniconda/condabin/conda' failed with exit code 1

The process '/usr/share/miniconda/condabin/conda' failed with exit code 1

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

Mamba support is still experimental and can result in differently solved environments!

UnsatisfiableError: The following specifications were found to be incompatible with the existing python installation in your environment: Specifications: - brotlipy -> python[version='3.10.*|3.4.*|3.6.12|3.6.12|3.7.10|3.7.10|3.7.12|3.8.12|3.9.10|3.7.9|3.6.9|3.6.9|3.6.9|3.6.9|3.11.*|3.9.*|3.8.*|3.7.*',build='0_73_pypy|4_73_pypy|0_73_pypy|0_73_pypy|1_73_pypy|5_73_pypy|5_73_pypy|3_73_pypy|2_73_pypy|1_73_pypy'] - certifi -> python[version='3.10.*|3.7.*|3.8.*|3.9.*'] - cffi -> python[version='2.7.*|3.5.*|3.6.*|3.6.12|3.6.12|3.7.10|3.7.10|3.7.12|3.8.12|3.9.10|>=3.10,<3.11.0a0|>=3.9,<3.10.0a0|>=3.11,<3.12.0a0|>=3.8,<3.9.0a0|>=3.7,<3.8.0a0|>=3.6,<3.7.0a0|3.7.9|3.6.9|3.6.9|3.6.9|>=2.7,<2.8.0a0|3.6.9|>=3.5,<3.6.0a0|3.4.*',build='0_73_pypy|4_73_pypy|0_73_pypy|0_73_pypy|1_73_pypy|5_73_pypy|5_73_pypy|3_73_pypy|2_73_pypy|1_73_pypy'] - conda-content-trust -> python[version='2.7.*|3.5.*|3.6.*|>=2.7,<2.8.0a0|>=3.6,<3.7.0a0|>=3.5,<3.6.0a0|3.4.*'] - cryptography -> python[version='3.10.*|3.6.12|3.6.12|3.7.10|3.7.10|3.7.12|3.8.12|3.9.10|3.7.9|3.6.9|3.6.9|3.6.9|3.6.9|3.8.*|3.11.*|3.9.*|3.7.*|3.4.*|>=3.6|>=3.5|<=3.3',build='0_73_pypy|4_73_pypy|0_73_pypy|0_73_pypy|1_73_pypy|5_73_pypy|5_73_pypy|3_73_pypy|2_73_pypy|1_73_pypy'] - jsonpointer -> python[version='2.7.*|3.5.*|3.6.*|3.4.*'] - packaging -> python[version='>=3.0,<=3.9'] - six -> python[version='2.7.*|3.5.*|3.6.*|>=2.7,<2.8.0a0|>=3.6,<3.7.0a0|>=3.8,<3.9.0a0|>=3.7,<3.8.0a0|3.4.*|>=3.9,<3.10.0a0|>=3.5,<3.6.0a0'] - zstandard -> python[version='3.10.*|3.11.*|3.6.12|3.6.12|3.7.10|3.7.10|3.7.12|3.8.12|3.9.10|3.7.9|3.6.9|3.6.9|3.6.9|3.6.9|>=3.5,<3.6.0a0|3.8.*|3.9.*|3.7.*',build='0_73_pypy|4_73_pypy|0_73_pypy|0_73_pypy|1_73_pypy|5_73_pypy|5_73_pypy|3_73_pypy|2_73_pypy|1_73_pypy'] Your python: python=3.11 If python is on the left-most side of the chain, that's the version you've asked for. When python appears to the right, that indicates that the thing on the left is somehow not available for the python version you are constrained to. Note that conda will not change your python version to a different minor version unless you explicitly specify that. The following specifications were found to be incompatible with a past explicit spec that is not an explicit spec in this operation (pip): - mamba -> conda[version='4.6.*|4.6.*|4.7.*|>=4.7.12,<4.13.0a0|>=4.8,<23.4|>=4.8,<5|>=4.8,<23.9.0a0|>=4.8,<4.13.0a0|>=4.7.12,<4.8'] - mamba -> conda[version='>=4.8,<23.4'] -> setuptools[version='>=31.0.1|>=60.0.0'] - mamba -> python[version='>=3.10,<3.11.0a0'] -> pip The following specifications were found to be incompatible with each other: Output in format: Requested package -> Available versions Package libgcc-ng conflicts for: c-ares -> libgcc-ng[version='>=11.2.0|>=4.9|>=7.3.0|>=7.5.0|>=9.3.0|>=9.4.0'] libssh2 -> openssl[version='>=1.1.1l,<1.1.2a'] -> libgcc-ng[version='>=10.3.0|>=4.9'] setuptools -> python[version='>=3.7'] -> libgcc-ng[version='>=10.3.0|>=12|>=9.4.0|>=9.3.0|>=7.5.0|>=7.3.0|>=4.9|>=11.2.0|>=7.2.0'] python=3.11 -> bzip2[version='>=1.0.8,<2.0a0'] -> libgcc-ng[version='>=10.3.0|>=7.3.0|>=7.5.0|>=9.3.0|>=9.4.0'] libsolv -> libgcc-ng[version='>=10.3.0|>=9.3.0|>=7.5.0|>=7.3.0|>=11.2.0'] libnghttp2 -> libgcc-ng[version='>=10.3.0|>=12|>=9.4.0|>=9.3.0|>=7.5.0|>=7.3.0|>=11.2.0'] requests -> python[version='>=3.7,<4.0'] -> libgcc-ng[version='>=10.3.0|>=12|>=9.4.0|>=9.3.0|>=7.5.0|>=7.3.0|>=4.9|>=11.2.0|>=7.2.0'] libmambapy -> python[version='>=3.9,<3.10.0a0'] -> libgcc-ng[version='>=4.9|>=7.3.0|>=9.3.0|>=7.2.0'] pysocks -> python[version='>=3.8'] -> libgcc-ng[version='>=10.3.0|>=12|>=9.4.0|>=9.3.0|>=7.5.0|>=7.3.0|>=11.2.0|>=4.9|>=7.2.0'] pcre2 -> libgcc-ng[version='>=11.2.0|>=12|>=9.3.0|>=7.5.0|>=7.3.0|>=4.9'] jsonpatch -> python[version='>=3.6'] -> libgcc-ng[version='>=10.3.0|>=12|>=9.4.0|>=9.3.0|>=7.5.0|>=7.3.0|>=4.9|>=11.2.0|>=7.2.0'] fmt -> libgcc-ng[version='>=11.2.0|>=12|>=9.4.0|>=9.3.0|>=7.5.0|>=7.3.0'] libcurl -> libgcc-ng[version='>=10.3.0|>=12|>=9.4.0|>=9.3.0|>=7.5.0|>=7.3.0|>=4.9|>=11.2.0|>=7.2.0'] cryptography -> cffi[version='>=1.12'] -> libgcc-ng[version='>=

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

Mamba support is still experimental and can result in differently solved environments!

UnsatisfiableError: The following specifications were found to be incompatible with the existing python installation in your environment: Specifications: - brotlipy -> python[version='3.10.*|3.4.*|3.6.12|3.6.12|3.7.10|3.7.10|3.7.12|3.8.12|3.9.10|3.7.9|3.6.9|3.6.9|3.6.9|3.6.9|3.11.*|3.9.*|3.8.*|3.7.*',build='2_73_pypy|3_73_pypy|4_73_pypy|5_73_pypy|0_73_pypy|0_73_pypy|1_73_pypy|5_73_pypy|1_73_pypy|0_73_pypy'] - certifi -> python[version='3.10.*|3.7.*|3.8.*|3.9.*'] - cffi -> python[version='2.7.*|3.5.*|3.6.*|3.6.12|3.6.12|3.7.10|3.7.10|3.7.12|3.8.12|3.9.10|>=3.10,<3.11.0a0|>=3.9,<3.10.0a0|>=3.11,<3.12.0a0|>=3.8,<3.9.0a0|>=3.7,<3.8.0a0|>=3.6,<3.7.0a0|3.7.9|3.6.9|3.6.9|3.6.9|>=2.7,<2.8.0a0|3.6.9|>=3.5,<3.6.0a0|3.4.*',build='2_73_pypy|3_73_pypy|4_73_pypy|5_73_pypy|0_73_pypy|0_73_pypy|1_73_pypy|5_73_pypy|1_73_pypy|0_73_pypy'] - conda-content-trust -> python[version='2.7.*|3.5.*|3.6.*|>=2.7,<2.8.0a0|>=3.6,<3.7.0a0|>=3.5,<3.6.0a0|3.4.*'] - cryptography -> python[version='3.10.*|3.6.12|3.6.12|3.7.10|3.7.10|3.7.12|3.8.12|3.9.10|3.7.9|3.6.9|3.6.9|3.6.9|3.6.9|3.8.*|3.11.*|3.9.*|3.7.*|3.4.*|>=3.6|>=3.5|<=3.3',build='2_73_pypy|3_73_pypy|4_73_pypy|5_73_pypy|0_73_pypy|0_73_pypy|1_73_pypy|5_73_pypy|1_73_pypy|0_73_pypy'] - jsonpointer -> python[version='2.7.*|3.5.*|3.6.*|3.4.*'] - packaging -> python[version='>=3.0,<=3.9'] - six -> python[version='2.7.*|3.5.*|3.6.*|>=2.7,<2.8.0a0|>=3.6,<3.7.0a0|>=3.8,<3.9.0a0|>=3.7,<3.8.0a0|3.4.*|>=3.9,<3.10.0a0|>=3.5,<3.6.0a0'] - zstandard -> python[version='3.10.*|3.11.*|3.6.12|3.6.12|3.7.10|3.7.10|3.7.12|3.8.12|3.9.10|3.7.9|3.6.9|3.6.9|3.6.9|3.6.9|>=3.5,<3.6.0a0|3.8.*|3.9.*|3.7.*',build='2_73_pypy|3_73_pypy|4_73_pypy|5_73_pypy|0_73_pypy|0_73_pypy|1_73_pypy|5_73_pypy|1_73_pypy|0_73_pypy'] Your python: python=3.11 If python is on the left-most side of the chain, that's the version you've asked for. When python appears to the right, that indicates that the thing on the left is somehow not available for the python version you are constrained to. Note that conda will not change your python version to a different minor version unless you explicitly specify that. The following specifications were found to be incompatible with a past explicit spec that is not an explicit spec in this operation (setuptools): - mamba -> conda[version='4.6.*|4.6.*|4.7.*|>=4.7.12,<4.13.0a0|>=4.8,<23.4|>=4.8,<5|>=4.8,<23.9.0a0|>=4.8,<4.13.0a0|>=4.7.12,<4.8'] - mamba -> conda[version='>=4.8,<23.4'] -> setuptools[version='>=31.0.1|>=60.0.0'] - mamba -> python[version='>=3.10,<3.11.0a0'] -> pip The following specifications were found to be incompatible with each other: Output in format: Requested package -> Available versions Package libnghttp2 conflicts for: libcurl -> libnghttp2[version='>=1.41.0,<2.0a0|>=1.43.0,<2.0a0|>=1.47.0,<2.0a0|>=1.57.0|>=1.57.0,<2.0a0|>=1.52.0|>=1.52.0,<2.0a0|>=1.46.0|>=1.46.0,<2.0a0'] mamba -> libcurl[version='>=7.79.1,<9.0a0'] -> libnghttp2[version='>=1.41.0,<2.0a0|>=1.43.0,<2.0a0|>=1.47.0,<2.0a0|>=1.57.0|>=1.57.0,<2.0a0|>=1.52.0|>=1.52.0,<2.0a0|>=1.46.0|>=1.46.0,<2.0a0'] libmamba -> libcurl[version='>=7.86.0,<9.0a0'] -> libnghttp2[version='>=1.41.0,<2.0a0|>=1.43.0,<2.0a0|>=1.46.0,<2.0a0|>=1.46.0|>=1.47.0,<2.0a0|>=1.57.0|>=1.57.0,<2.0a0|>=1.52.0|>=1.52.0,<2.0a0'] Package libuuid conflicts for: conda==23.5.2 -> python[version='>=3.11,<3.12.0a0'] -> libuuid[version='>=1.0.3,<2.0a0|>=1.41.5,<2.0a0|>=2.32.1,<3.0a0'] urllib3 -> python[version='<4.0'] -> libuuid[version='>=1.0.3,<2.0a0|>=1.41.5,<2.0a0|>=2.32.1,<3.0a0'] conda-package-streaming -> python[version='>=3.9'] -> libuuid[version='>=1.0.3,<2.0a0|>=1.41.5,<2.0a0|>=2.32.1,<3.0a0'] pluggy -> python[version='>=3.8'] -> libuuid[version='>=1.0.3,<2.0a0|>=1.41.5,<2.0a0|>=2.32.1,<3.0a0'] python=3.11 -> libuuid[version='>=1.41.5,<2.0a0|>=2.32.1,<3.0a0'] pycosat -> python[version='>=3.9,<3.10.0a0'] -> libuuid[version='>=1.0.3,<2.0a0|>=1.41.5,<2.0a0|>=2.32.1,<3.0a0'] setuptools -> python[version='>=3.7'] -> libuuid[version='>=1.0.3,<2.0a0|>=1.41.5,<2.0a0|>=2.32.1,<3.0a0'] jsonpatch -> python[version='>=3.6'] -> libuuid[version='>=1

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

Mamba support is still experimental and can result in differently solved environments!

UnsatisfiableError: The following specifications were found to be incompatible with the existing python installation in your environment: Specifications: - brotlipy -> python[version='3.10.*|3.4.*|3.6.12|3.6.12|3.7.10|3.7.10|3.7.12|3.8.12|3.9.10|3.7.9|3.6.9|3.6.9|3.6.9|3.6.9|3.11.*|3.9.*|3.8.*|3.7.*',build='3_73_pypy|5_73_pypy|1_73_pypy|0_73_pypy|0_73_pypy|5_73_pypy|4_73_pypy|2_73_pypy|1_73_pypy|0_73_pypy'] - certifi -> python[version='3.10.*|3.7.*|3.8.*|3.9.*'] - cffi -> python[version='2.7.*|3.5.*|3.6.*|3.6.12|3.6.12|3.7.10|3.7.10|3.7.12|3.8.12|3.9.10|>=3.10,<3.11.0a0|>=3.9,<3.10.0a0|>=3.11,<3.12.0a0|>=3.8,<3.9.0a0|>=3.7,<3.8.0a0|>=3.6,<3.7.0a0|3.7.9|3.6.9|3.6.9|3.6.9|>=2.7,<2.8.0a0|3.6.9|>=3.5,<3.6.0a0|3.4.*',build='3_73_pypy|5_73_pypy|1_73_pypy|0_73_pypy|0_73_pypy|5_73_pypy|4_73_pypy|2_73_pypy|1_73_pypy|0_73_pypy'] - conda-content-trust -> python[version='2.7.*|3.5.*|3.6.*|>=2.7,<2.8.0a0|>=3.6,<3.7.0a0|>=3.5,<3.6.0a0|3.4.*'] - cryptography -> python[version='3.10.*|3.6.12|3.6.12|3.7.10|3.7.10|3.7.12|3.8.12|3.9.10|3.7.9|3.6.9|3.6.9|3.6.9|3.6.9|3.8.*|3.11.*|3.9.*|3.7.*|3.4.*|>=3.6|>=3.5|<=3.3',build='3_73_pypy|5_73_pypy|1_73_pypy|0_73_pypy|0_73_pypy|5_73_pypy|4_73_pypy|2_73_pypy|1_73_pypy|0_73_pypy'] - jsonpointer -> python[version='2.7.*|3.5.*|3.6.*|3.4.*'] - packaging -> python[version='>=3.0,<=3.9'] - six -> python[version='2.7.*|3.5.*|3.6.*|>=2.7,<2.8.0a0|>=3.6,<3.7.0a0|>=3.8,<3.9.0a0|>=3.7,<3.8.0a0|3.4.*|>=3.9,<3.10.0a0|>=3.5,<3.6.0a0'] - zstandard -> python[version='3.10.*|3.11.*|3.6.12|3.6.12|3.7.10|3.7.10|3.7.12|3.8.12|3.9.10|3.7.9|3.6.9|3.6.9|3.6.9|3.6.9|>=3.5,<3.6.0a0|3.8.*|3.9.*|3.7.*',build='3_73_pypy|5_73_pypy|1_73_pypy|0_73_pypy|0_73_pypy|5_73_pypy|4_73_pypy|2_73_pypy|1_73_pypy|0_73_pypy'] Your python: python=3.11 If python is on the left-most side of the chain, that's the version you've asked for. When python appears to the right, that indicates that the thing on the left is somehow not available for the python version you are constrained to. Note that conda will not change your python version to a different minor version unless you explicitly specify that. The following specifications were found to be incompatible with a past explicit spec that is not an explicit spec in this operation (conda): - mamba -> conda[version='4.6.*|4.6.*|4.7.*|>=4.7.12,<4.13.0a0|>=4.8,<23.4|>=4.8,<5|>=4.8,<23.9.0a0|>=4.8,<4.13.0a0|>=4.7.12,<4.8'] - mamba -> conda[version='>=4.8,<23.4'] -> setuptools[version='>=31.0.1|>=60.0.0'] - mamba -> python[version='>=3.10,<3.11.0a0'] -> pip The following specifications were found to be incompatible with each other: Output in format: Requested package -> Available versions Package python_abi conflicts for: urllib3 -> python_abi[version='2.7.*|3.8.*|3.6.*|3.6|3.7.*',build='*_cp36m|*_cp38|*_cp27mu|*_pypy36_pp73|*_cp37m'] libmambapy -> python_abi[version='3.10.*|3.11.*|3.9|3.8.*|3.9.*|3.8|3.7.*|3.7',build='*_pypy39_pp73|*_cp310|*_cp311|*_cp38|*_cp39|*_pypy38_pp73|*_cp37m|*_pypy37_pp73'] zstandard -> python_abi[version='3.10.*|3.11.*|3.8.*|3.9.*|3.8|3.9|3.7.*|3.7|3.6.*|3.6',build='*_cp36m|*_pypy39_pp73|*_pypy38_pp73|*_cp310|*_cp311|*_cp38|*_cp39|*_cp37m|*_pypy37_pp73|*_pypy36_pp73'] pysocks -> python_abi[version='2.7.*|3.10.*|3.7.*|3.8.*|3.9|3.8|3.9.*|3.7|3.6.*|3.6',build='*_pypy36_pp73|*_cp36m|*_pypy37_pp73|*_pypy38_pp73|*_pypy39_pp73|*_cp38|*_cp37m|*_cp310|*_cp39|*_cp27mu'] setuptools -> python_abi[version='3.10.*|3.7.*|3.9.*|3.9|3.8.*|3.8|3.7|3.11.*|3.6.*|3.6',build='*_cp36m|*_pypy39_pp73|*_cp310|*_cp39|*_cp37m|*_cp38|*_pypy38_pp73|*_pypy37_pp73|*_cp311|*_pypy36_pp73'] mamba -> python_abi[version='3.10.*|3.11.*|3.9|3.8.*|3.9.*|3.8|3.7.*|3.7|3.6.*|3.6',build='*_pypy36_pp73|*_cp36m|*_pypy39_pp73|*_cp310|*_cp311|*_cp38|*_cp39|*_pypy38_pp73|*_cp37m|*_pypy37_pp73'] conda-package-streaming -> python[version='>=3.9'] -> python_abi[version='2.7.*|3.6.*|3.6|3.8.*|3.9|3.7.*|3.11.*|3.9.*|3.10.*|3.8|3.7',build='*_cp310|*_cp36m|*_cp37m|*_pypy39_pp73|*_cp38|*_pypy36_pp73|*_cp27mu|*_cp311|*_cp39|*_pypy38_pp73|*_pypy37_pp73'] ruamel.yaml -> python_abi[version='2.7.*|3.10

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

Mamba support is still experimental and can result in differently solved environments!

UnsatisfiableError: The following specifications were found to be incompatible with the existing python installation in your environment: Specifications: - brotlipy -> python[version='3.10.*|3.4.*|3.6.12|3.6.12|3.7.10|3.7.10|3.7.12|3.8.12|3.9.10|3.7.9|3.6.9|3.6.9|3.6.9|3.6.9|3.11.*|3.9.*|3.8.*|3.7.*',build='0_73_pypy|1_73_pypy|3_73_pypy|5_73_pypy|0_73_pypy|0_73_pypy|1_73_pypy|5_73_pypy|4_73_pypy|2_73_pypy'] - certifi -> python[version='3.10.*|3.7.*|3.8.*|3.9.*'] - cffi -> python[version='2.7.*|3.5.*|3.6.*|3.6.12|3.6.12|3.7.10|3.7.10|3.7.12|3.8.12|3.9.10|>=3.10,<3.11.0a0|>=3.9,<3.10.0a0|>=3.11,<3.12.0a0|>=3.8,<3.9.0a0|>=3.7,<3.8.0a0|>=3.6,<3.7.0a0|3.7.9|3.6.9|3.6.9|3.6.9|>=2.7,<2.8.0a0|3.6.9|>=3.5,<3.6.0a0|3.4.*',build='0_73_pypy|1_73_pypy|3_73_pypy|5_73_pypy|0_73_pypy|0_73_pypy|1_73_pypy|5_73_pypy|4_73_pypy|2_73_pypy'] - conda-content-trust -> python[version='2.7.*|3.5.*|3.6.*|>=2.7,<2.8.0a0|>=3.6,<3.7.0a0|>=3.5,<3.6.0a0|3.4.*'] - cryptography -> python[version='3.10.*|3.6.12|3.6.12|3.7.10|3.7.10|3.7.12|3.8.12|3.9.10|3.7.9|3.6.9|3.6.9|3.6.9|3.6.9|3.8.*|3.11.*|3.9.*|3.7.*|3.4.*|>=3.6|>=3.5|<=3.3',build='0_73_pypy|1_73_pypy|3_73_pypy|5_73_pypy|0_73_pypy|0_73_pypy|1_73_pypy|5_73_pypy|4_73_pypy|2_73_pypy'] - jsonpointer -> python[version='2.7.*|3.5.*|3.6.*|3.4.*'] - packaging -> python[version='>=3.0,<=3.9'] - six -> python[version='2.7.*|3.5.*|3.6.*|>=2.7,<2.8.0a0|>=3.6,<3.7.0a0|>=3.8,<3.9.0a0|>=3.7,<3.8.0a0|3.4.*|>=3.9,<3.10.0a0|>=3.5,<3.6.0a0'] - zstandard -> python[version='3.10.*|3.11.*|3.6.12|3.6.12|3.7.10|3.7.10|3.7.12|3.8.12|3.9.10|3.7.9|3.6.9|3.6.9|3.6.9|3.6.9|>=3.5,<3.6.0a0|3.8.*|3.9.*|3.7.*',build='0_73_pypy|1_73_pypy|3_73_pypy|5_73_pypy|0_73_pypy|0_73_pypy|1_73_pypy|5_73_pypy|4_73_pypy|2_73_pypy'] Your python: python=3.11 If python is on the left-most side of the chain, that's the version you've asked for. When python appears to the right, that indicates that the thing on the left is somehow not available for the python version you are constrained to. Note that conda will not change your python version to a different minor version unless you explicitly specify that. The following specifications were found to be incompatible with a past explicit spec that is not an explicit spec in this operation (pip): - mamba -> conda[version='4.6.*|4.6.*|4.7.*|>=4.7.12,<4.13.0a0|>=4.8,<23.4|>=4.8,<5|>=4.8,<23.9.0a0|>=4.8,<4.13.0a0|>=4.7.12,<4.8'] - mamba -> conda[version='>=4.8,<23.4'] -> setuptools[version='>=31.0.1|>=60.0.0'] - mamba -> python[version='>=3.10,<3.11.0a0'] -> pip The following specifications were found to be incompatible with each other: Output in format: Requested package -> Available versions Package libgcc-ng conflicts for: reproc -> libgcc-ng[version='>=7.5.0|>=9.4.0'] mamba -> libgcc-ng[version='>=7.3.0|>=7.5.0|>=9.3.0|>=9.4.0'] conda-package-streaming -> python[version='>=3.9'] -> libgcc-ng[version='>=10.3.0|>=12|>=9.4.0|>=9.3.0|>=7.5.0|>=11.2.0|>=7.3.0|>=4.9|>=7.2.0'] libarchive -> libgcc-ng[version='>=10.3.0|>=12|>=9.4.0|>=9.3.0|>=7.5.0|>=7.3.0|>=4.9|>=11.2.0|>=7.2.0'] libxml2 -> libgcc-ng[version='>=10.3.0|>=12|>=9.4.0|>=9.3.0|>=7.5.0|>=7.3.0|>=4.9|>=11.2.0|>=7.2.0'] libedit -> ncurses[version='>=6.2,<7.0.0a0'] -> libgcc-ng[version='>=10.3.0|>=9.4.0'] libmambapy -> python[version='>=3.9,<3.10.0a0'] -> libgcc-ng[version='>=4.9|>=7.3.0|>=9.3.0|>=7.2.0'] libev -> libgcc-ng[version='>=4.9|>=7.3.0|>=7.5.0'] krb5 -> openssl[version='>=1.1.1l,<1.1.2a'] -> libgcc-ng[version='>=12'] krb5 -> libgcc-ng[version='>=10.3.0|>=9.4.0|>=9.3.0|>=7.5.0|>=7.3.0|>=4.9|>=11.2.0|>=7.2.0'] libssh2 -> libgcc-ng[version='>=11.2.0|>=12|>=9.4.0|>=9.3.0|>=7.5.0|>=7.3.0|>=7.2.0'] cffi -> libgcc-ng[version='>=11.2.0|>=12|>=9.4.0|>=9.3.0|>=7.5.0|>=7.3.0|>=4.9|>=7.2.0'] brotlipy -> libgcc-ng[version='>=10.3.0|>=12|>=9.4.0|>=9.3.0|>=7.5.0|>=7.3.0|>=4.9|>=11.2.0'] libsolv -> libgcc-ng[version='>=10.3.0|>=9.3.0|>=7.5.0|>=7.3.0|>=11.2.0'] packaging -> python[version='>=3.6'] -> libgcc-ng[version='>=10.3.0|>=12|>=9.4.0|>=9.3.0|>=7.5.0|>=7.3.0|>=4.9|>=11.2.0|>=7.2.0'] icu -> libgcc-ng[version='>=10.3.0|>=9.4

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

Mamba support is still experimental and can result in differently solved environments!