Skip to content

Conversation

Tobias-Fischer
Copy link

@Tobias-Fischer Tobias-Fischer commented Jul 31, 2025

See #98

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.

@Tobias-Fischer
Copy link
Author

@conda-forge-admin, please rerender

@conda-forge-admin
Copy link
Contributor

conda-forge-admin commented Jul 31, 2025

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:

  • ❌ When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
  • ❌ When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
  • ❌ When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
  • ❌ When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
  • ❌ When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
  • ❌ When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
  • ❌ When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
  • ❌ When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
  • ❌ When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
  • ❌ When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
  • ❌ When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
  • ❌ When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
  • ❌ When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
  • ❌ When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
  • ❌ When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
  • ❌ When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
  • ❌ When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
  • ❌ When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
  • ❌ When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).

For recipe/meta.yaml:

  • ℹ️ The recipe is not parsable by parser conda-forge-tick (the bot). Your recipe may not receive automatic updates and/or may not be compatible with conda-forge's infrastructure. Please check the logs for more information and ensure your recipe can be parsed.
  • ℹ️ 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.

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

@Tobias-Fischer
Copy link
Author

This wasn't a 1:1 backport - if someone could take a proper look at the PR and review it that'd be great.

Copy link
Member

@h-vetinari h-vetinari left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks 🙏

(But will let maintainers here chime in)

@h-vetinari
Copy link
Member

@conda-forge-admin, please rerender

@napetrov
Copy link
Contributor

@Tobias-Fischer thanks a lot for preparing this !

@napetrov napetrov merged commit 13209e2 into conda-forge:mkl/2024.X Jul 31, 2025
10 of 11 checks passed
@Tobias-Fischer Tobias-Fischer deleted the patch-1 branch July 31, 2025 19:36
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.

4 participants