protobuf v6.33.4#261
Conversation
…6.01.12.02.27.58 Other tools: - conda-build 25.11.1 - rattler-build 0.55.0 - rattler-build-conda-compat 1.4.10
|
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/meta.yaml:
This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/21164827583. Examine the logs at this URL for more detail. |
|
Paging Doctor Bazel, paging Doctor Bazel... (==@xhochy) 😅 I cannot find anything in the protobuf sources about |
|
Awesome, thanks a lot @xhochy! :) Windows is still unhappy though: |
On Windows, Python is installed as python.exe, but rules_python looks for python3 on PATH. This causes the build to fail with "interpreter not found: Unable to find the binary 'python3' on PATH". Fix by copying python.exe to python3.exe before running bazel. Co-Authored-By: Claude <noreply@anthropic.com>
|
Seems like this could be related to conda-forge/python-feedstock#640 |
|
Yeah, makes sense. Looks like it's working now 🥳 I'll forcepush out the debug & rerender commits; no need to have this kind of delete&recreate churn in the feedstock history. |
|
I guess we should fix this in the python-feedstock? Otherwise, we will need to create and delete python3.exe here. |
You're a maintainer there, you can revive that PR. :) I'm fine to carry this hack on the feedstock for now. It's a small concern compared to everything else we need to do to get grpc/protobuf off the ground |
No description provided.