Bug 2341745

Summary: gala: FTBFS in Fedora Rawhide
Product: [Fedora] Fedora Reporter: Fabio Valentini <decathorpe>
Component: galaAssignee: Fabio Valentini <decathorpe>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 42CC: benson_muite, decathorpe, pantheon-sig
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
URL: https://koschei.fedoraproject.org/package/gala
Whiteboard:
Fixed In Version: gala-8.2.3^20250610.git42ab42a-1.fc43 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-06-16 12:38:10 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: 2300528, 2338727, 2341542    

Description Fabio Valentini 2025-01-23 12:17:14 UTC
Description of problem:
Package gala fails to build from source in Fedora Rawhide.

Version-Release number of selected component (if applicable):
8.1.0-2.fc42

Steps to Reproduce:
koji build --scratch f42 gala-8.1.0-2.fc42.src.rpm

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

Reproducible: Always

Comment 1 Aoife Moloney 2025-02-26 13:48:41 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 42 development cycle.
Changing version to 42.

Comment 2 Fedora Update System 2025-06-16 12:34:13 UTC
FEDORA-2025-80d214ca1c (gala-8.2.3^20250610.git42ab42a-1.fc43 and wingpanel-8.0.3^20250611.git7990904-1.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-80d214ca1c

Comment 3 Fedora Update System 2025-06-16 12:38:10 UTC
FEDORA-2025-80d214ca1c (gala-8.2.3^20250610.git42ab42a-1.fc43 and wingpanel-8.0.3^20250611.git7990904-1.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.