Closed samtygier-stfc closed 1 month ago
I think this is happening in the conda mambabuild $GITHUB_WORKSPACE/conda
. possibly because the build-env
is created with Python 3.11. It then tries to install python 3.12 and gets confused because it needs something older than 3.12.0 to stay happy with 3.11, but does not want to install an RC version.
It is because conda-verify
does not have a 3.12 supporting package on conda-forge https://github.com/conda-forge/conda-verify-feedstock/issues/40
conda create -n build-env --yes boa anaconda-client conda-verify
Gives a python 3.11 environment
conda create -n build-env --yes boa anaconda-client conda-verify python=3.12
Fails with error python 3.12** is not installable because there are no viable options
conda create -n build-env --yes boa anaconda-client
Gives a python 3.12 environment
Don't think we used verify, so maybe should just remove it.
Summary
The publish package workflow is currently failing: https://github.com/mantidproject/mantidimaging/actions/runs/10202443842/job/28226566696
Steps To Reproduce
Happens when actions runs on a merge to main
Expected Behaviour
Builds package
Current Behaviour
Fails
Context
Happening since the Python 3.12 update
Failure Logs