chore(deps): require python-build in conda recipe #107
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I saw conda builds in CI on #106 failing like this:
Looks to me like this is due to the following set of circumstances:
build
This fixes that by switching the dependency in the recipe from
build
topython-build
.Notes for Reviewers
I'm really not sure why this is just breaking now... the latest release of
build
at https://anaconda.org/conda-forge/build/files is a noarch package without any constraints that appear to conflict with other things we're installing here.python-build
is what we want either way, since it's being actively updated, but would be good to understand why this just broke now.I checked across the
rapidsai
org and don't see any other cases where we were relying on the oldbuild
package: https://github.com/search?q=org%3Arapidsai+%22-+build%22+language%3AYAML+path%3Ameta.yaml&type=code