Bug 2385658 - sugar-pippy: FTBFS in Fedora rawhide/f43
Summary: sugar-pippy: FTBFS in Fedora rawhide/f43
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: sugar-pippy
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ibiam Chihurumnaya
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F43FTBFS
TreeView+ depends on / blocked
 
Reported: 2025-07-31 11:13 UTC by Fedora Release Engineering
Modified: 2025-07-31 11:14 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:

Attachments (Terms of Use)
build.log (3.06 KB, text/plain)
2025-07-31 11:13 UTC, Fedora Release Engineering 		no flags Details
root.log (32.00 KB, text/plain)
2025-07-31 11:14 UTC, Fedora Release Engineering 		no flags Details
state.log (1.50 KB, text/plain)
2025-07-31 11:14 UTC, Fedora Release Engineering 		no flags Details
View All

Description Fedora Release Engineering 2025-07-31 11:13:52 UTC 
sugar-pippy failed to build from source in Fedora rawhide/f43

https://koji.fedoraproject.org/koji/taskinfo?taskID=135268142


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_43_Mass_Rebuild
Please fix sugar-pippy at your earliest convenience and set the bug's status to
ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks,
sugar-pippy will be orphaned. Before branching of Fedora 44,
sugar-pippy will be retired, if it still fails to build.

For more details on the FTBFS policy, please visit:
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
Comment 1 Fedora Release Engineering 2025-07-31 11:13:56 UTC 
Created attachment 2101869 [details]
build.log
Comment 2 Fedora Release Engineering 2025-07-31 11:14:02 UTC 
Created attachment 2101870 [details]
root.log

file root.log too big, will only attach last 32768 bytes
Comment 3 Fedora Release Engineering 2025-07-31 11:14:05 UTC 
Created attachment 2101871 [details]
state.log
Note You need to log in before you can comment on or make changes to this bug.