You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Opening an issue to track when the rattler-build fix has propagated so we can start publishing builds again, I think I gave the wrong impression that while fixes have been merged, they aren't yet deployed all the way to the conda-forge build environment.
Specifically, we need a release with prefix-dev/rattler-build#1406 which I assume will be 0.35.10. 0.35.9 doesn't have it, at least. We'll need to make sure the build is run with that version before we merge a PR. I can double-check the repodata as well.
Opening an issue to track when the rattler-build fix has propagated so we can start publishing builds again, I think I gave the wrong impression that while fixes have been merged, they aren't yet deployed all the way to the conda-forge build environment.
Specifically, we need a release with prefix-dev/rattler-build#1406 which I assume will be 0.35.10. 0.35.9 doesn't have it, at least. We'll need to make sure the build is run with that version before we merge a PR. I can double-check the repodata as well.
The latest broken builds have been yanked: conda-forge/admin-requests#1370
We can't easily do repodata patches, because repodata patching doesn't work with these packages that don't follow the schema.
The text was updated successfully, but these errors were encountered: