Closed kmod closed 2 years ago
You should report this issue to @conda-forge/conda-smithy and ask for help there. We recipe maintainers do not have control on the rerender process (unless we have a bug in conda_build_config.yaml
).
Hi, unfortunately I can't access that link.
I don't know enough whether to say that the current situation is a bug in conda_build_config.yaml, but I'll put up a draft PR with a change to that file that causes the rerender to succeed. Hopefully that better describes what I'm getting at, and then we can determine if it's a bug in the yaml or in conda-smithy.
It is almost always a bug in conda-smithy: https://github.com/conda-forge/conda-smithy Please help us file an issue there because this is apparently a regression (which I can reproduce locally), thanks!
Sure thing, I filed it as https://github.com/conda-forge/conda-smithy/issues/1615
I did my best to convey your points, but I don't personally have the context to know that this is a bug in conda-smithy so they might ask you to chime in.
Thanks, @kmod. I replied in the issue. It's a bug in conda-smithy.
Solution to issue cannot be found in the documentation.
Issue
When I try to rerender I get the following:
The value of
pkg_pins
is'x.x'
. I'm not super familiar with this whole system, but maybe you need some dashes in the conda_build_config.yaml file so that it gets interpreted as a list? Just a guess.Installed packages
Environment info