Use newer lief again

[h-vetinari]

No description provided.

[conda-forge-webservices]

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.

[h-vetinari]

Stuck (again) on conda-forge/boa-feedstock#75

[jaimergp]

We might need updated lower bounds for conda-build & conda so we update conda 23.3 (as bundled in Miniforge right now) to at least 23.7.4, which will also bring a more recent conda-libmamba-solver.

We might also force this via remote_ci_setup?

[jaimergp]

We might need mamba>=1.5.2 there too, I think.

[h-vetinari]

Alright, that's a combination that works! 🥳

[isuruf]

@conda-forge-admin, rerender

[h-vetinari]

For some reason, even though it's not specified in the conda install step, something seems to try to pull in an exact mamba version that's too old:

├─ mamba 1.4.2  is installable with the potential options
         ^^^^^
         why pinned?

[h-vetinari]

Do we still need these lines with conda-forge-ci-setup=4?

[jaimergp]

Yep, ci-setup is going to nudge the solvers to obtain the "latest everything" but the conda-smithy config is still needed here because the default is still "mamba + mambabuild". In the (not so long!) future, when conda-build + conda-libmamba-solver is default we can omit this section.

[h-vetinari]

something seems to try to pull in an exact mamba version that's too old:

Should be solved by conda-forge/conda-forge-ci-setup-feedstock#290; I'll restart

[h-vetinari]

Nope, still getting lost with looking for 1.4.2, possibly because that's what's there after the mambaforge install.

[jaimergp]

That might be a manifestation of an conda-libmamba-solver bug. The miniforge we are using bundles 23.3 and that one was a bit stubborn about the history if things were not explicitly mentioned in the CLI. Maybe using conda_install_tool=mamba helps? I'll add a comment.

[jaimergp]

@conda-forge-admin, rerender