Marcel Bargull

Then this is a regression. This always worked with `conda-build 2.1.x`.

``` $ conda-build --version conda-build 2.1.18 $ conda render . package: name: cc-pack version: '0.1' source: path: ../ build: entry_points: - cc_test = cc_pack.do_stuff:main script: python setup.py install requirements: build:...

Thanks for letting us know about the 0.12.3 release. There have been multiple Mach-O-related (segfault) fixes, so this could very well help :).

FYI, I've done the same in gh-399 while also removing the then not needed fallback to `ruamel_yaml`.

Issue with `conda=23.11`, see https://github.com/conda/conda/issues/13400#issue-2025834712 . You can install `conda install conda=23.10` for now to get things working again.

> But obviously, it's unfortunate that this wasn't caught by a CI system ahead of time. We shall improve that by more conservative version pinning of the conda dependency in...

> repodata patch forcing 1.5.3 to be installed with conda

> Yes, please, please, please do add a `mamba` test to the `conda` feedstock. We can add a `downstreams` test to `conda-feedstock`, yes. That being said, those tests should really...

> > repodata patch forcing 1.5.3 to be installed with conda > We already put in a repodata patch on conda-forge for this. I just checked if it works as...

Oh, sorry, I have to correct myself: `mamba update mamba` is the only one that *does* work (i.e., updates to `mamba=1.5.4`). But all the others (`mamba update conda`, `CONDA_SOLVER=libmamba conda...