Closed larsoner closed 2 months ago
Okay I looked at git log
and noticed that a recent merge to main
succeeded with a previous conda-forge-pinning
, so I did:
MNT: Re-rendered with conda-build 24.5.2.dev41, conda-smithy 3.36.3.dev46+gdd6091b8, and conda-forge-pinning 2024.07.04.12.04.07
so that made me look at https://github.com/conda-forge/vtk-feedstock/pull/330 where someone manually rebuilt with a dev version of conda-smithy and conda-build. So I git clone'ed conda-build
and conda-smithy
(checking out dd6091b8), pip install -ve .
'ed them and did conda install rattler-build-conda-compat
and then:
conda-smithy rerender --no-check-uptodate -c auto
and things were fine. So I guess this was fixed in #1969 so I'll close!
Solution to issue cannot be found in the documentation.
Issue
See https://github.com/conda-forge/vtk-feedstock/pull/332 and https://github.com/conda-forge/vtk-feedstock/actions/runs/9847400200/job/27187287542. Replicated locally using up-to-date conda-smithy in a clean env just created using
conda create -n smithy conda-smithy
. To replicate, clone theconda-forge/vtk-feedstock
and try to rerender it.The error is:
Installed packages
Environment info