Closed alinelena closed 1 year ago
Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe
) and found it was in an excellent condition.
this looks like an issue of conda-forge to me (unrelated to QE)?
RuntimeError: Solver could not find solution.Mamba failed to solve:
- wget
- libgomp
- openmpi-mpifort
- m4
- make
- gfortran_linux-64 12.*
- gcc_linux-64 12.*
- cmake >=3.18.0
with channels:
The reported errors are:
- Encountered problems while solving:
- - package gcc_linux-64-12.2.0-h4798a0e_11 requires gcc_impl_linux-64 12.2.0.*, but none of the providers can be installed
-
yes this seems to be the case. looks like an inconsistent update of the compilers on conda side. I notice in a clean install I have gcc 11.3
@ltalirz something else which is odd my last pipeline seems to pick 12.1 rather than 12.2 like in the error message you posted.
- - package gfortran_linux-64-12.1.0-h7ec3724_10 requires gfortran_impl_linux-64 12.1.0.*, but none of the providers can be installed
i tried to fix the compiler versions but somehow still picks the 12 variants.
let me see if we can enable the better error messages in boa and then we would have more informative output. I suspect that some of the dependencies need to be rebuilt for the latest compilers. cc @AntoinePrv
Superseded by #40. @alinelena I hope you don't mind.
I think the reason for pinning compiler was not working, is that you make a commit after the conda forge render, which will not automatically update things from recipe/meta.yaml
. The tip is to not pull after the render bot makes the commit but always force push and then trigger the render.
@conda-forge-admin please rerender
Checklist
0
(if the version changed)conda-smithy
(Use the phrase code>@<space/conda-forge-admin, please rerender in a comment in this PR for automated rerendering)