Bug 2488340

Summary:	syslog-ng: FTBFS in Fedora Rawhide: Problem: package protobuf-c-compiler-1.5.2-3.fc45.aarch64 from build requires libprotoc.so.33.5.0()(64bit), but none of the providers can be installed
Product:	[Fedora] Fedora	Reporter:	Karolina Surma <ksurma>
Component:	syslog-ng	Assignee:	Peter Czanik <peter>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	code, mrunge, peter
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Linux
URL:	https://koschei.fedoraproject.org/package/syslog-ng
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2026-06-24 06:07:52 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2412434, 2433833

Description Karolina Surma 2026-06-12 13:29:04 UTC

Description of problem:
Package syslog-ng fails to build from source in Fedora Rawhide.

Version-Release number of selected component (if applicable):
4.11.0-1.fc45

Steps to Reproduce:
koji build --scratch f45 syslog-ng-4.11.0-1.fc45.src.rpm

Additional info:
This package is tracked by Koschei. See:
https://koschei.fedoraproject.org/package/syslog-ng

Reproducible: Always

Actual Results:
DEBUG util.py:461:  Problem: package protobuf-c-compiler-1.5.2-3.fc45.aarch64 from build requires libprotoc.so.33.5.0()(64bit), but none of the providers can be installed
DEBUG util.py:461:    - package protobuf-compiler-33.5-5.fc45.aarch64 from build conflicts with protobuf3-compiler provided by protobuf3-compiler-3.19.6-64.fc45.aarch64 from build
DEBUG util.py:461:    - package protobuf-c-devel-1.5.2-3.fc45.aarch64 from build requires protobuf-c-compiler(aarch-64) = 1.5.2-3.fc45, but none of the providers can be installed
DEBUG util.py:461:    - package grpc-cpp-1.48.4-61.fc45.aarch64 from build requires libprotoc.so.30()(64bit), but none of the providers can be installed
DEBUG util.py:461:    - package riemann-c-client-devel-1.10.5-14.fc44.aarch64 from build requires protobuf-c-devel(aarch-64), but none of the providers can be installed
DEBUG util.py:461:    - package grpc-devel-1.48.4-61.fc45.aarch64 from build requires libgrpc++.so.1.48()(64bit), but none of the providers can be installed
DEBUG util.py:461:    - package grpc-devel-1.48.4-61.fc45.aarch64 from build requires libgrpc++_reflection.so.1.48()(64bit), but none of the providers can be installed
DEBUG util.py:461:    - package grpc-devel-1.48.4-61.fc45.aarch64 from build requires libgrpc++_unsecure.so.1.48()(64bit), but none of the providers can be installed
DEBUG util.py:461:    - package grpc-devel-1.48.4-61.fc45.aarch64 from build requires libgrpc_plugin_support.so.1.48()(64bit), but none of the providers can be installed
DEBUG util.py:461:    - package grpc-devel-1.48.4-61.fc45.aarch64 from build requires libgrpc++_alts.so.1.48()(64bit), but none of the providers can be installed
DEBUG util.py:461:    - package grpc-devel-1.48.4-61.fc45.aarch64 from build requires libgrpc++_error_details.so.1.48()(64bit), but none of the providers can be installed
DEBUG util.py:461:    - package grpc-devel-1.48.4-61.fc45.aarch64 from build requires libgrpcpp_channelz.so.1.48()(64bit), but none of the providers can be installed
DEBUG util.py:461:    - package grpc-devel-1.48.4-61.fc45.aarch64 from build requires grpc-cpp(aarch-64) = 1.48.4-61.fc45, but none of the providers can be installed

Comment 1 Ben Beasley 2026-06-16 05:24:53 UTC

I looked into this a little, because this will prevent me from rebuilding syslog-ng for the upcoming abseil-cpp update.

The syslog-ng package requires protobuf-devel < 4, that is, protobuf3-devel, when the grpc bcond is enabled. Because grpc is stuck at an old version (historically, due to protobuf being too old, and now just because it’s painful to update and nobody has put in the work), the protobuf dependency does have to be v3 to match grpc.

The syslog-ng package requires riemann-c-client for the riemann subpackage; riemann-c-client, in turn, requires protobuf-devel (the updated version). So does collectd, which also depends on riemann-c-client, so riemann-c-client cannot be pinned to protobuf-devel < 4 without breaking collectd.

The protobuf3-devel package requires protobuf3-compiler, and protobuf-devel requires protobuf-compiler, and protobuf3-compiler and protobuf-devel conflict because they both provide /usr/bin/protoc. Even if this weren’t true, protobuf3-devel and protobuf-devel would conflict directly.

Long-term, the best fix will be for somebody to update grpc to a current release that uses a current protobuf. Short-term, I don’t see anything that can be done other than for syslog-ng to choose to drop *either* the subpackages that need grpc (-grpc, -opentelemetry, -loki, -bigquery, -clickhouse, -pubsub), *or* the subpackage that requires riemann-c-client (-riemann).

Maintainers of syslog-ng, what do you think?

Comment 2 Peter Czanik 2026-06-16 06:51:56 UTC

I'll disable riemann-c-client support today. I know that grpc-based destinations are in active use in Fedora, while riemann is AFAIK only used by some RHEL users.

Comment 3 Peter Czanik 2026-06-16 09:48:44 UTC

OK. Syslog-ng build with riemann support disabled is now submitted to Rawhide: https://bodhi.fedoraproject.org/updates/FEDORA-2026-628f1715f7

Comment 4 Ben Beasley 2026-06-24 06:07:52 UTC

Closing this since the issue has been worked around.