Skip to content

MKL 2025.3#150

Merged
isuruf merged 4 commits into
conda-forge:mainfrom
mgorny:mkl2
Oct 28, 2025
Merged

MKL 2025.3#150
isuruf merged 4 commits into
conda-forge:mainfrom
mgorny:mkl2

Conversation

@mgorny

@mgorny mgorny commented Oct 28, 2025

Copy link
Copy Markdown
Contributor

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.

Forking #128 to try again, in small steps, but without erasing the history.

@conda-forge-admin

conda-forge-admin commented Oct 28, 2025

Copy link
Copy Markdown
Contributor

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:

  • ❌ You're setting a constraint on the __osx virtual package 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.

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

@mgorny

mgorny commented Oct 28, 2025

Copy link
Copy Markdown
Contributor Author

Excellent, so 2025.0 fails, 2025.2 works. 2025.3 was merged a while ago, so let's wait for that to finish building and I'll update the PR.

Signed-off-by: Michał Górny <mgorny@gentoo.org>
Signed-off-by: Michał Górny <mgorny@gentoo.org>
@mgorny mgorny changed the title MKL 2025.2, attempt two MKL 2025.3 Oct 28, 2025
…5.10.28.12.55.54

Other tools:
- conda-build 25.9.0
- rattler-build 0.48.1
- rattler-build-conda-compat 1.4.9

Signed-off-by: Michał Górny <mgorny@gentoo.org>
@mgorny mgorny marked this pull request as ready for review October 28, 2025 18:50
Signed-off-by: Michał Górny <mgorny@gentoo.org>
@isuruf isuruf added the automerge Merge the PR when CI passes label Oct 28, 2025
@conda-forge-admin

Copy link
Copy Markdown
Contributor

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

I considered the following status checks when analyzing this PR:

  • linter: failed
  • azure: passed

Thus the PR was not passing and not merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automerge Merge the PR when CI passes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants