Skip to content

BUG: Add default value for CF_TORCH_CUDA_ARCH_LIST_BACKUP in deactivate.sh#489

Closed
carterbox wants to merge 3 commits into
conda-forge:mainfrom
carterbox:bug/unbound-variables
Closed

BUG: Add default value for CF_TORCH_CUDA_ARCH_LIST_BACKUP in deactivate.sh#489
carterbox wants to merge 3 commits into
conda-forge:mainfrom
carterbox:bug/unbound-variables

Conversation

@carterbox
Copy link
Copy Markdown
Member

@carterbox carterbox commented Feb 20, 2026

Checklist

  • Used a personal fork of the feedstock to propose changes
  • Bumped the build number (if the version is unchanged)
  • Reset the build number to 0 (if the version changed)
  • Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
  • Ensured the license file is being packaged.

As reported here: conda-forge/cuda-nvcc-feedstock#92 and here: conda-forge/ctng-compiler-activation-feedstock#175, conda 26.1 will raise an error if an activate/deactivate script tries to evaluate an unbound environment variable.

In this MR, I add the default value syntax (:-) to the evaluation of CF_TORCH_CUDA_ARCH_LIST_BACKUP in the deactivate script such that if the activation script does not set this variable, then the deactivation script will not fail.

EDIT: This only seems to occur when gdb is also in the environment.

…6.02.20.18.04.36

Other tools:
- conda-build 25.11.1
- rattler-build 0.55.1
- rattler-build-conda-compat 1.4.10
@conda-forge-admin
Copy link
Copy Markdown
Contributor

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:

  • ℹ️ The magma output has been superseded by libmagma-devel.
  • ℹ️ The recipe is not parsable by parser conda-souschef (grayskull). This parser is not currently used by conda-forge, but may be in the future. We are collecting information to see which recipes are compatible with grayskull.
  • ℹ️ The recipe is not parsable by parser conda-recipe-manager. The recipe can only be automatically migrated to the new v1 format if it is parseable by conda-recipe-manager.

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

@h-vetinari
Copy link
Copy Markdown
Member

Thanks for the PR. We'll queue this up with the next round of builds. :)

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.

3 participants