Build llama.cpp b5289 - #125
Conversation
|
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 ( I do have some suggestions for making it better though... For recipe/recipe.yaml:
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. |
|
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 |
We should do this, but that should happen on main. I moved this to a special branch. |
|
Hi! This is the friendly conda-forge automerge bot! I considered the following status checks when analyzing this PR:
Thus the PR was passing and merged! Have a great day! |
Checklist
0(if the version changed)conda-smithy(Use the phrase@conda-forge-admin, please rerenderin a comment in this PR for automated rerendering)Summary
Sets the feedstock to build llama.cpp upstream tag
b5289(recipe version5289).This build fills a gap:
b5289is currently missing from conda-forge even though it is required by downstream packages such asllama-cpp-server-py-core.The recipe's test suite had to be reconciled with what that older tree actually installs.