Bug 2380974

Summary:	cairo-dock-plug-ins: FTBFS with change proposal CMake: Use ninja generator by default
Product:	[Fedora] Fedora	Reporter:	Cristian Le <fedora>
Component:	cairo-dock-plug-ins	Assignee:	Mamoru TASAKA <mtasaka>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	mtasaka
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2025-07-17 11:23:06 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:	2376112

Description Cristian Le 2025-07-16 15:11:55 UTC

Dear package maintainer,

This is an automated bug created due to a FTBFS when rebuilding this package for the change proposal CMake: Use ninja generator by default.

The rebuild is being tracked in https://copr.fedorainfracloud.org/coprs/lecris/cmake-ninja/package/cairo-dock-plug-ins.

See https://fedoraproject.org/wiki/Changes/CMake_ninja_default for more information on how to make the package compatible.

More specifically, make sure you are using standard %cmake_* macros. If you find that there are hard dependencies on
the generator even after such transition, please ping me for closer investigation.

You can check the build locally following the instructions in the change proposal, or submit your build to the tracking
copr project.

Let me know if you encounter any issues, or need any other help.

Comment 1 Mamoru TASAKA 2025-07-16 23:47:09 UTC

This is because buildroot uses old cairo-dock: you are using 3.5.99^20250623git6b5d476-1.rc3, but 3.5.99^20250714gite852048-1.rc6.fc42 is needed.

Comment 2 Cristian Le 2025-07-17 11:23:06 UTC

Probably. It failed 3 months ago also. It seems like it would be hard to properly impact check against this package, so if it FTBFS when the change proposal is merged, feel free to ping me and we can look at it together. For now we can close it as unrelated.