jaimergp

> Do we need a release of ezomero then? So then I should update the recipe for the new version of ezomero? A fix upstream plus a new release would...

@psobolewskiPhD, we don't have a conclusion on the [bioconda conflict](https://github.com/conda-forge/staged-recipes/pull/25329#issuecomment-3141106322) yet, right?

It looks like the Python metadata has an unknown version: ``` ?rw-rw-r-- 0/0 5 2025-08-08 13:41:59 site-packages/ezomero-0.0.0.dist-info/INSTALLER ?rw-rw-r-- 0/0 2712 2025-08-08 13:41:57 site-packages/ezomero-0.0.0.dist-info/METADATA ?rw-rw-r-- 0/0 1656 2025-08-08 13:41:57 site-packages/ezomero-0.0.0.dist-info/RECORD ?rw-rw-r--...

This repository is for `--solver=libmamba`. Can you try that instead of classic?

That's a problem with the classic solver, not conda-libmamba-solver, unfortunately. There's a workaround though. You can leverage `conda-standalone` for this, as a one-time thing: 1. Fetch the [latest conda-standalone](https://github.com/conda/conda-standalone/releases/tag/24.5.0) for...

Ok, I see... Can you try this one now? ``` conda.exe install -p C:\Users\david\anaconda3 "conda>=23.10" conda-libmamba-solver python --override-channels -c defaults --strict-channel-priority ```

There have been several iterations in Azure (see https://github.com/Microsoft/azure-pipelines-agent/issues/1270), so we had to combine different "skipper" formulas to make sure we were not triggering CI services in large migrations (e.g....

> The GitHub Actions cf linter does not run on the PR though. Uhh yea, that's not great. @beckermr, what do you think about this? Does it interact with the...

Thanks @wshanks, ended up adding https://github.com/conda-forge/conda-smithy/pull/2077 and https://github.com/conda-forge/staged-recipes/pull/27765 for Azure via your suggestion.

> I'm not sure it makes sense to just record the package name (+ some other id?) in each environment, as there is a full package list afterwards with that...