Bug 2504403 - phosh-tour: FTBFS in Fedora rawhide/f45
Summary: phosh-tour: FTBFS in Fedora rawhide/f45
Keywords:
Status: CLOSED COMPLETED
Alias: None
Product: Fedora
Classification: Fedora
Component: phosh-tour
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Sam Day
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: F45FTBFS
TreeView+ depends on / blocked
 
Reported: 2026-07-21 20:45 UTC by Fedora Release Engineering
Modified: 2026-07-30 07:32 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2026-07-30 07:32:23 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
build.log (17.61 KB, text/plain)
2026-07-21 20:45 UTC, Fedora Release Engineering 		no flags Details
root.log (32.00 KB, text/plain)
2026-07-21 20:45 UTC, Fedora Release Engineering 		no flags Details
state.log (1.65 KB, text/plain)
2026-07-21 20:45 UTC, Fedora Release Engineering 		no flags Details
View All

Description Fedora Release Engineering 2026-07-21 20:45:17 UTC 
phosh-tour failed to build from source in Fedora rawhide/f45

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


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_45_Mass_Rebuild
Please fix phosh-tour 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,
phosh-tour will be orphaned. Before branching of Fedora 46,
phosh-tour 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 2026-07-21 20:45:23 UTC 
Created attachment 2151118 [details]
build.log
Comment 2 Fedora Release Engineering 2026-07-21 20:45:28 UTC 
Created attachment 2151119 [details]
root.log

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