This is a tracking bug for Change: Protobuf 5.x/6.x For more details, see: https://fedoraproject.org/wiki/Changes/Protobuf_5.x/6.x Update Protobuf to the latest version (5.x), and 6.x if it arrives in time before freeze in Q1 2025. Note that Protobuf's versioning is complicated, C++ and Python are at version 5, other language bindings at version 4, and they all embed the version of protoc; we are using the C++ version here so we can reference its support policy. If you encounter a bug related to this Change, please do not comment here. Instead create a new bug and set it to block this bug.
Hi Michel, this is a reminder that the testable deadline is coming up in about two weeks, on Feb 4th, and changes need to be in good shape at this point https://docs.fedoraproject.org/en-US/program_management/changes_policy/#_change_process_milestones for Beta. Please let me know if you need to defer this to F43, otherwise if youre good to go for the change to be ready to meet the testable requirements, please update the status of the tracker bug to MODIFIED. Thanks! Aoife
(In reply to Aoife Moloney from comment #1) > Hi Michel, this is a reminder that the testable deadline is coming up in > about two weeks, on Feb 4th, and changes need to be in good shape at this > point > https://docs.fedoraproject.org/en-US/program_management/changes_policy/ > #_change_process_milestones for Beta. > > Please let me know if you need to defer this to F43, otherwise if youre good > to go for the change to be ready to meet the testable requirements, please > update the status of the tracker bug to MODIFIED. > > > Thanks! > Aoife Hi Aoife, let's defer this to F43 anyway just to be sure. The compatibility package is done, but we want to make sure the rewrite of the newer protobuf package itself is done properly, so it's better to land it in Rawhide first, then if that goes well and we have an urgent need we can consider following the incompatible upgrades policy to bring it to F42
Ack, deferring to F43 as requested. Thanks!
Dear change owner, this is a reminder that your change is required to be 100% code complete by August 26, which is the start of beta freeze. Please provide a status update on your change in the Incomplete Changes Report if you are not able to move your change to 'ON_QA' before this date. If you need to defer your change to the next Fedora release, please let me know and I will reassign this bug and the change page. Thank you kindly.
FYI, this is one of multiple issues currently breaking ceph-mgr in Fedora. python-protobuf v3 is broken with subinterpreters. AIUI 4 onwards are fixed.
Turns out upstream has a workaround for this already (using the Python impl). Still, worth noting the impact (subinterpreter brokenness).
Retargeting change as per FESCo decision in https://pagure.io/fesco/issue/3465
https://copr.fedorainfracloud.org/coprs/mochaa/protobuf/ I have protobuf v32.1 + grpc v1.74.1 + gtest v1.17.0 ready here, need a mentor to guide me how to do large rebuilds
Hi, what is the current progress? The F44 testable deadline is coming soon and the Fedora 'protobuf' package was still not rebased to 5.x version and last update to this tracker BZ was months ago. The COPR has tons of recent builds, but hard to tell if that's an active development or automation feeding it there. Could you please provide at least rough overview on the progress, and whether it's likely the Change will made it to F44 or not? Thanks!
Hi michel, how goes this change for F44? The testable deadline is today, February 03, 2026, and changes need to be in good shape at this point https://docs.fedoraproject.org/en-US/program_management/changes_policy/#_change_process_milestones Please let me know if you need to defer this to F45, otherwise if you're good to go for the change to be ready to meet the testable requirements, please update the status of the tracker bug to MODIFIED. Thanks!
Please see https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/YZD7KV2CQV567BKT5IKCFP2DHVOB3OSL/ first. I'm working on protobuf v33.5 (maybe 34.0 if it releases) and gRPC 1.78.0. This change is not good enough yet to be included in F44, deferring this.