public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
To: git-commits@fedoraproject.org
Subject: [rpms/CuraEngine_grpc_definitions] rawhide: Use protobuf in version 3.x only
Date: Sat, 06 Jun 2026 07:38:13 GMT [thread overview]
Message-ID: <178073149373.1.3519814673104338017.rpms-CuraEngine_grpc_definitions-8462a9b115a9@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/CuraEngine_grpc_definitions
Branch : rawhide
Commit : 8462a9b115a9ee2883da273fe397e207662d1119
Author : Miroslav Suchý <msuchy@redhat.com>
Date : 2026-05-14T11:37:58+02:00
Stats : +1/-1 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/CuraEngine_grpc_definitions/c/8462a9b115a9ee2883da273fe397e207662d1119?branch=rawhide
Log:
Use protobuf in version 3.x only
This is part of https://fedoraproject.org/wiki/Changes/Protobuf_5.x/6.x
This package does not sucessfully build with new protobuf per
https://copr.fedorainfracloud.org/coprs/mochaa/protobuf/monitor/
so limiting to protobuf version 3.
Once the protobuf is rebase this will automatically pick up compat
package protobuf3
I am not bumping release as this does not need a rebuild now.
---
diff --git a/CuraEngine_grpc_definitions.spec b/CuraEngine_grpc_definitions.spec
index a63866a..abb7444 100644
--- a/CuraEngine_grpc_definitions.spec
+++ b/CuraEngine_grpc_definitions.spec
@@ -14,7 +14,7 @@ BuildRequires: cmake
BuildRequires: gcc-c++
BuildRequires: grpc-devel
BuildRequires: asio-grpc-devel
-BuildRequires: protobuf-devel
+BuildRequires: protobuf-devel < 4
BuildRequires: zlib-devel
BuildRequires: openssl-devel
BuildRequires: c-ares-devel
reply other threads:[~2026-06-06 7:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=178073149373.1.3519814673104338017.rpms-CuraEngine_grpc_definitions-8462a9b115a9@fedoraproject.org \
--to=git-commits@fedoraproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox