Bug 2226424 - setools: FTBFS in Fedora rawhide/f39
Summary: setools: FTBFS in Fedora rawhide/f39
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: setools
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Petr Lautrbach
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F39FTBFS
TreeView+ depends on / blocked
 
Reported: 2023-07-25 20:09 UTC by Fedora Release Engineering
Modified: 2023-07-26 16:51 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2023-07-26 16:51:31 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
build.log (13.06 KB, text/plain)
2023-07-25 20:09 UTC, Fedora Release Engineering
no flags Details
root.log (32.00 KB, text/plain)
2023-07-25 20:09 UTC, Fedora Release Engineering
no flags Details
state.log (1015 bytes, text/plain)
2023-07-25 20:09 UTC, Fedora Release Engineering
no flags Details

Description Fedora Release Engineering 2023-07-25 20:09:13 UTC
setools failed to build from source in Fedora rawhide/f39

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


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild
Please fix setools 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,
setools will be orphaned. Before branching of Fedora 40,
setools 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 2023-07-25 20:09:18 UTC
Created attachment 1979634 [details]
build.log

Comment 2 Fedora Release Engineering 2023-07-25 20:09:21 UTC
Created attachment 1979635 [details]
root.log

file root.log too big, will only attach last 32768 bytes

Comment 3 Fedora Release Engineering 2023-07-25 20:09:24 UTC
Created attachment 1979636 [details]
state.log


Note You need to log in before you can comment on or make changes to this bug.