Bug 2301238 - reg: FTBFS in Fedora rawhide/f41
Summary: reg: FTBFS in Fedora rawhide/f41
Keywords:
Status: CLOSED COMPLETED
Alias: None
Product: Fedora
Classification: Fedora
Component: reg
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Fedora Infrastructure SIG
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F41FTBFS
TreeView+ depends on / blocked
 
Reported: 2024-07-29 21:07 UTC by Fedora Release Engineering
Modified: 2024-08-06 09:32 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-08-06 09:32:28 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
build.log (3.05 KB, text/plain)
2024-07-29 21:07 UTC, Fedora Release Engineering 		no flags Details
root.log (32.00 KB, text/plain)
2024-07-29 21:07 UTC, Fedora Release Engineering 		no flags Details
state.log (1.48 KB, text/plain)
2024-07-29 21:07 UTC, Fedora Release Engineering 		no flags Details
View All

Description Fedora Release Engineering 2024-07-29 21:07:03 UTC 
reg failed to build from source in Fedora rawhide/f41

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


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_41_Mass_Rebuild
Please fix reg 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,
reg will be orphaned. Before branching of Fedora 42,
reg 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 2024-07-29 21:07:09 UTC 
Created attachment 2042621 [details]
build.log
Comment 2 Fedora Release Engineering 2024-07-29 21:07:14 UTC 
Created attachment 2042622 [details]
root.log

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