Bug 2340003

Summary: cpio: FTBFS in Fedora rawhide/f42
Product: [Fedora] Fedora Reporter: Fedora Release Engineering <releng>
Component: cpioAssignee: Pavel Raiskup <praiskup>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 42CC: ljavorsk, ovasik, pkubat, praiskup
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: cpio-2.15-4.fc42 cpio-2.15-5.fc43 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-04-01 16:09:14 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: 2260875, 2300528    
Attachments:
Description Flags
build.log
none
root.log
none
state.log none

Description Fedora Release Engineering 2025-01-22 19:19:04 UTC
cpio failed to build from source in Fedora rawhide/f42

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


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_42_Mass_Rebuild
Please fix cpio 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,
cpio will be orphaned. Before branching of Fedora 43,
cpio 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-01-22 19:19:07 UTC
Created attachment 2068592 [details]
build.log

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

Comment 2 Fedora Release Engineering 2025-01-22 19:19:09 UTC
Created attachment 2068593 [details]
root.log

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

Comment 3 Fedora Release Engineering 2025-01-22 19:19:10 UTC
Created attachment 2068594 [details]
state.log

Comment 4 Fedora Release Engineering 2025-01-22 20:51:07 UTC
*** Bug 2339620 has been marked as a duplicate of this bug. ***

Comment 5 Fedora Update System 2025-01-24 15:25:16 UTC
FEDORA-2025-b0fe175865 (cpio-2.15-4.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-b0fe175865

Comment 6 Fedora Update System 2025-02-06 00:00:17 UTC
FEDORA-2025-47ab3cb89d (cpio-2.15-4.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-47ab3cb89d

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

Comment 8 Fedora Update System 2025-03-28 13:09:30 UTC
FEDORA-2025-a00bc023c2 (cpio-2.15-4.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-a00bc023c2

Comment 9 Fedora Update System 2025-03-29 01:31:32 UTC
FEDORA-2025-a00bc023c2 has been pushed to the Fedora 42 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-a00bc023c2`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-a00bc023c2

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 10 Fedora Update System 2025-04-01 16:09:14 UTC
FEDORA-2025-a00bc023c2 (cpio-2.15-4.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 11 Fedora Update System 2025-06-20 14:43:40 UTC
FEDORA-2025-389104ac12 (cpio-2.15-5.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-389104ac12

Comment 12 Fedora Update System 2025-07-24 14:31:11 UTC
FEDORA-2025-389104ac12 (cpio-2.15-5.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.