Skip to content

Build llama.cpp b5289 - #125

Merged
conda-forge-admin merged 1 commit into
conda-forge:b5289from
pb01ka:5289
Jul 21, 2026
Merged

Build llama.cpp b5289#125
conda-forge-admin merged 1 commit into
conda-forge:b5289from
pb01ka:5289

Conversation

@pb01ka

@pb01ka pb01ka commented Jul 21, 2026

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.

Summary

Sets the feedstock to build llama.cpp upstream tag b5289 (recipe version 5289).

This build fills a gap: b5289 is currently missing from conda-forge even though it is required by downstream packages such as llama-cpp-server-py-core.

The recipe's test suite had to be reconciled with what that older tree actually installs.

@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/recipe.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipe/recipe.yaml:

  • ℹ️ 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/29848348678. Examine the logs at this URL for more detail.

@pb01ka
pb01ka marked this pull request as ready for review July 21, 2026 18:04
@pb01ka

pb01ka commented Jul 21, 2026

Copy link
Copy Markdown
Contributor Author

The tests are passing. I request the reviewers to please take a look at it. @frankier @jjerphan @jonashaag @pavelzw @traversaro @xhochy

@xhochy As per your earlier comment, should I switch osx_arm64_ and win_64_ to Azure runners? Please let me know. TY.

@xhochy
xhochy changed the base branch from main to b5289 July 21, 2026 18:43
@xhochy

xhochy commented Jul 21, 2026

Copy link
Copy Markdown
Member

@xhochy As per your conda-forge/rignore-feedstock#1 (comment), should I switch osx_arm64_ and win_64_ to Azure runners? Please let me know.

We should do this, but that should happen on main. I moved this to a special branch.

@xhochy xhochy added the automerge Merge the PR when CI passes label Jul 21, 2026
@conda-forge-admin
conda-forge-admin merged commit b0d59f5 into conda-forge:b5289 Jul 21, 2026
15 checks passed
@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: passed
  • azure: passed
  • github-actions: passed

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

@pb01ka
pb01ka deleted the 5289 branch July 21, 2026 18:58
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.

3 participants