Add package for linux-riscv64

[luhenry]

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.

[luhenry]

cc @isuruf

[conda-forge-admin]

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 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/31039528777. Examine the logs at this URL for more detail.}

[luhenry]

@conda-forge-admin, please rerender

[conda-forge-admin]

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 GitHub Actions workflow below for more details. You can also ping conda-forge/core (using the @ notation) for further assistance or you can try rerendering locally.

The following suggestions might help debug any issues:

• Is the recipe/{meta.yaml,recipe.yaml} file valid?
• If there is a recipe/conda-build-config.yaml file in the feedstock make sure that it is compatible with the current global pinnings.
• Is the fork used for this PR on an organization or user GitHub account? Automated rerendering via the webservices admin bot only works for user GitHub accounts.

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

[luhenry]

Re-rendering locally

[luhenry]

Depends on conda-forge/conda-forge-pinning-feedstock#8721 ✅

[luhenry]

@isuruf @xhochy this only adds the link+sha256 for the riscv64 upstream .tar.xz package, it doesn't create the conda package just yet. For this kind of change, should we add it proactively until a migrator submits the linux-riscv64 change, or should we wait for that migration PR and push to it?

[h-vetinari]

now that the migration has started, some packages are beginning to require a rust compile (example: conda-forge/ripgrep-feedstock#40). Would be good to pick this up again

[luhenry]

Should I open a PR against conda-forge/feedstock-outputs to register rust-std-riscv64gc-unknown-linux-gnu as a valid feedstock output? AFAIU it should be automatic once this PR is merged to main otherwise?

[luhenry]

@isuruf @xhochy please let me know if there is anything else to be done for this one. It blocks a few other for lack of rust.

[isuruf]

Yes, please send a PR to admin-requests

[isuruf]

See https://github.com/conda-forge/admin-requests/blob/main/examples/example-add-feedstock-output.yml

[isuruf]

and https://github.com/conda-forge/admin-requests#add-a-package-output-to-a-feedstock

[luhenry]

conda-forge/admin-requests#2244 ✅

[dbast]

green + admin requests PR is merged :)

[pkgw]

Looks good to me, but I'm not fully up-to-speed on all of the compiler infra.