Skip to content

avoid using cuda_compiler as selector #243

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 7 commits into
base: main
Choose a base branch
from

Conversation

conda-forge-admin
Copy link
Contributor

Hi! This is the friendly automated conda-forge-webservice.

I've started rerendering the recipe as instructed in #242.

If I find any needed changes to the recipe, I'll push them to this PR shortly. Thank you for waiting!

Here's a checklist to do before merging.

Fixes #242

@conda-forge-admin
Copy link
Contributor Author

conda-forge-admin commented May 30, 2025

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipe/meta.yaml:

  • ℹ️ py-xgboost output has some malformed specs:
  • In section host: libxgboost =*=cpu_h*_PKG_BUILDNUM
  • In section run: libxgboost =*=cpu_h*_PKG_BUILDNUM
    xgboost output has some malformed specs:
  • In section host: py-xgboost =*=cpu_pyh*_PKG_BUILDNUM
  • In section run: py-xgboost =*=cpu_pyh*_PKG_BUILDNUM
    r-xgboost output has some malformed specs:
  • In section host: libxgboost =*=cpu_h*_PKG_BUILDNUM
  • In section run: libxgboost =*=cpu_h*_PKG_BUILDNUM
    Requirement spec fields should match the syntax name [version [build]]to avoid known issues in conda-build. For example, instead of name =version=build, use name version.* build. There should be no spaces between version operators and versions either: python >= 3.8 should be python >=3.8.

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/15339081860. Examine the logs at this URL for more detail.

@conda-forge-admin conda-forge-admin marked this pull request as ready for review May 30, 2025 04:12
@h-vetinari h-vetinari changed the title MNT: rerender avoid using cuda_version as selector May 30, 2025
@conda-forge-admin
Copy link
Contributor Author

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

@h-vetinari
Copy link
Member

Cannot remove the equal-signs (to make linter happy) without breaking the recipe:

conda_build.exceptions.RecipeError: Mismatching hashes in recipe. Exact pins in dependencies that contribute to the hash often cause this. Can you change one or more exact pins to version bound constraints?
Involved packages were:
Mismatching package: libxgboost (id cuda128_hacb7753_1); dep: libxgboost * cuda128_h*_1; consumer package: py-xgboost
Mismatching package: libxgboost (id cuda128_hacb7753_1); dep: libxgboost * cuda128_h*_1; consumer package: py-xgboost
Mismatching package: libxgboost (id cuda128_hacb7753_1); dep: libxgboost * cuda128_h*_1; consumer package: r-xgboost
Mismatching package: libxgboost (id cuda128_hacb7753_1); dep: libxgboost * cuda128_h*_1; consumer package: r-xgboost

@conda-forge-admin
Copy link
Contributor Author

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipe/meta.yaml:

  • ℹ️ py-xgboost output has some malformed specs:
  • In section host: libxgboost =*=cpu_h*_PKG_BUILDNUM
  • In section run: libxgboost =*=cpu_h*_PKG_BUILDNUM
    xgboost output has some malformed specs:
  • In section host: py-xgboost =*=cpu_pyh*_PKG_BUILDNUM
  • In section run: py-xgboost =*=cpu_pyh*_PKG_BUILDNUM
    r-xgboost output has some malformed specs:
  • In section host: libxgboost =*=cpu_h*_PKG_BUILDNUM
  • In section run: libxgboost =*=cpu_h*_PKG_BUILDNUM
    Requirement spec fields should match the syntax name [version [build]]to avoid known issues in conda-build. For example, instead of name =version=build, use name version.* build. There should be no spaces between version operators and versions either: python >= 3.8 should be python >=3.8.

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/15339244895. Examine the logs at this URL for more detail.

@h-vetinari h-vetinari force-pushed the conda_forge_admin_242 branch from 93e6256 to 04c903f Compare May 30, 2025 04:39
@conda-forge-admin
Copy link
Contributor Author

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

@h-vetinari h-vetinari changed the title avoid using cuda_version as selector avoid using cuda_compiler as selector Jun 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

@conda-forge-admin, please rerender
2 participants