libprotobuf v29.0

[regro-cf-autotick-bot]

It is very likely that the current package version for this feedstock is out of date.

Checklist before merging this PR:

• Dependencies have been updated if changed: see upstream
• Tests have passed
• Updated license if changed and license_file is packaged

Information about this PR:

1. Feel free to push to the bot's branch to update this PR if needed.
2. The bot will almost always only open one PR per version.
3. The bot will stop issuing PRs if more than 3 version bump PRs generated by the bot are open. If you don't want to package a particular version please close the PR.
4. If you want these PRs to be merged automatically, make an issue with @conda-forge-admin,please add bot automerge in the title and merge the resulting PR. This command will add our bot automerge feature to your feedstock.
5. If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase @conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

Pending Dependency Version Updates

Here is a list of all the pending dependency version updates for this repo. Please double check all dependencies before merging.

Name	Upstream Version	Current Version
libprotobuf	29.0

_{This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/cf-scripts/actions/runs/12059690913 - please use this URL for debugging.}

[conda-forge-admin]

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

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

For recipe/meta.yaml:

• ℹ️ The recipe is not parsable by parser conda-souschef (grayskull). 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-recipe-manager. 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.

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

[h-vetinari]

Seems that protobuf has started shipping upb:

+ test '!' -d $PREFIX/include/upb
WARNING: Tests failed for libprotobuf-5.29.0-h5b01275_0.conda - moving package to /home/conda/feedstock_root/build_artifacts/broken

Our libgrpc builds still contain:

lib/libupb_base_lib.so
lib/libupb_json_lib.so
lib/libupb_mem_lib.so
lib/libupb_message_lib.so
lib/libupb_mini_descriptor_lib.so
lib/libupb_textformat_lib.so
lib/libupb_wire_lib.so

though not the headers. I guess we could try flipping

libprotobuf-feedstock/recipe/build-lib.sh

Line 48 in bd12801

-Dprotobuf_BUILD_LIBUPB=OFF \

and seeing if we can make grpc use our own upb in protobuf. As always, this relates to protocolbuffers/protobuf#12927

[mariusvniekerk]

At this point should we just ship the upb headers as part of libprotobuf or libprotobuf-dev ? The lack of a claimed stable abi is a concern obviously.