Update for CUDA12.6.0

[adibbley]

xref:

• Update for CUDA 12.6.0 cuda-feedstock#38
• Migrate CTK packages to {{ stdlib("c") }} cuda-feedstock#26

[conda-forge-webservices]

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

I wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found some lint.

Here's what I've got...

For recipe/meta.yaml:

• This recipe is using a compiler, which now requires adding a build dependence on {{ stdlib("c") }} as well. Note that this rule applies to each output of the recipe using a compiler. For further details, please see META: {{ stdlib("c") }} migration conda-forge.github.io#2102.
• You're setting a requirement on sysroot_linux- directly; this should now be done by adding a build dependence on {{ stdlib("c") }}, and overriding c_stdlib_version in recipe/conda_build_config.yaml for the respective platform as necessary. For further details, please see META: {{ stdlib("c") }} migration conda-forge.github.io#2102.

[conda-forge-webservices]

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

I wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found some lint.

Here's what I've got...

For recipe/meta.yaml:

• This recipe is using a compiler, which now requires adding a build dependence on {{ stdlib("c") }} as well. Note that this rule applies to each output of the recipe using a compiler. For further details, please see META: {{ stdlib("c") }} migration conda-forge.github.io#2102.

[adibbley]

@conda-forge-admin, please restart ci

[adibbley]

@conda-forge-admin, please restart ci

[adibbley]

@conda-forge-admin, please lint

[conda-forge-webservices]

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

I wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found some lint.

Here's what I've got...

For recipe/meta.yaml:

• This recipe is using a compiler, which now requires adding a build dependence on {{ stdlib("c") }} as well. Note that this rule applies to each output of the recipe using a compiler. For further details, please see META: {{ stdlib("c") }} migration conda-forge.github.io#2102.

[conda-forge-webservices]

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.

[jakirkham]

@conda-forge-admin, please rerender

[github-actions]

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

I tried to rerender for you but ran into some issues. Please check the output logs of the latest webservices GitHub actions workflow run for errors. You can also ping conda-forge/core for further assistance or you can try rerendeing locally.

This message was generated by GitHub actions workflow run https://github.com/conda-forge/cuda-nvcc-impl-feedstock/actions/runs/10220814745.

[adibbley]

I've been hitting that rerender error as well, doing it locally does work though.

[jakirkham]

The re-rendering is complaining it did not know how to define platform in this block

cuda-nvcc-impl-feedstock/recipe/meta.yaml

Lines 7 to 9 in 938b371

	{% set platform = "linux-x86_64" %} # [linux64]
	{% set platform = "linux-ppc64le" %} # [ppc64le]
	{% set platform = "linux-sbsa" %} # [aarch64]

[jakirkham]

What version of conda-build do you have locally?

[adibbley]

24.5.0

[jakirkham]

Ok so maybe this is a bug with the recently released conda-build version 24.7.1: conda-forge/conda-build-feedstock#229

Edit: Interesting that building the package doesn't run into this issue. Must have something to do with where conda-smithy hooks into conda-build

[jakirkham]

Just to confirm, are you using conda-smithy version 3.37.2?

[adibbley]

Yes

[jakirkham]

@robertmaynard am assuming this is ok since this is dropped from the source file. We were not patching this line. Though please let us know if we need to change anything here

[jakirkham]

Ah missed Rob is out today. Think we should be ok here. So let's go ahead and merge

We can follow up with Rob when he get back

[adibbley]

Pulled your changes and local rerender had no further changes, adding automerge. Thanks John!

[github-actions]

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

• linter: passed
• azure: passed

Thus the PR was passing and merged! Have a great day!

[jakirkham]

Regarding the re-rendering issue, filed upstream issue: conda-forge/conda-smithy#2011