Bug 2341605

Summary: zmap: FTBFS in Fedora rawhide/f42
Product: [Fedora] Fedora Reporter: Fedora Release Engineering <releng>
Component: zmapAssignee: Filipe Rosset <rosset.filipe>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 42CC: rosset.filipe
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: zmap-4.3.4-1.fc43 zmap-4.3.4-1.fc42 zmap-4.3.4-1.el10_2 zmap-4.3.4-1.el10_1 zmap-4.3.4-1.el9 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-11-17 02:45:28 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: 2300528    
Attachments:
Description Flags
build.log
none
root.log
none
state.log none

Description Fedora Release Engineering 2025-01-22 22:27:40 UTC
zmap failed to build from source in Fedora rawhide/f42

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


For details on the mass rebuild see:

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

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

Comment 2 Fedora Release Engineering 2025-01-22 22:27:44 UTC
Created attachment 2073339 [details]
root.log

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

Comment 3 Fedora Release Engineering 2025-01-22 22:27:46 UTC
Created attachment 2073340 [details]
state.log

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

Comment 5 Fedora Update System 2025-11-09 06:29:52 UTC
FEDORA-2025-7e98f31eb9 (zmap-4.3.4-1.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-7e98f31eb9

Comment 6 Fedora Update System 2025-11-09 06:29:53 UTC
FEDORA-2025-31768106de (zmap-4.3.4-1.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-31768106de

Comment 7 Fedora Update System 2025-11-09 06:29:53 UTC
FEDORA-EPEL-2025-dbcc451897 (zmap-4.3.4-1.el9) has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-dbcc451897

Comment 8 Fedora Update System 2025-11-10 01:22:42 UTC
FEDORA-2025-7e98f31eb9 has been pushed to the Fedora 43 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-7e98f31eb9`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-7e98f31eb9

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

Comment 9 Fedora Update System 2025-11-10 02:02:00 UTC
FEDORA-2025-31768106de 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-31768106de`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-31768106de

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

Comment 10 Fedora Update System 2025-11-10 03:28:23 UTC
FEDORA-EPEL-2025-e83933c0ea has been pushed to the Fedora EPEL 10.2 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-e83933c0ea

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

Comment 11 Fedora Update System 2025-11-10 03:38:26 UTC
FEDORA-EPEL-2025-8d1d9dbf02 has been pushed to the Fedora EPEL 10.1 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-8d1d9dbf02

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

Comment 12 Fedora Update System 2025-11-10 03:41:33 UTC
FEDORA-EPEL-2025-dbcc451897 has been pushed to the Fedora EPEL 9 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-dbcc451897

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

Comment 13 Fedora Update System 2025-11-17 02:45:28 UTC
FEDORA-2025-7e98f31eb9 (zmap-4.3.4-1.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 14 Fedora Update System 2025-11-18 01:18:40 UTC
FEDORA-2025-31768106de (zmap-4.3.4-1.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 15 Fedora Update System 2025-11-18 01:51:10 UTC
FEDORA-EPEL-2025-e83933c0ea (zmap-4.3.4-1.el10_2) has been pushed to the Fedora EPEL 10.2 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 16 Fedora Update System 2025-11-18 02:01:41 UTC
FEDORA-EPEL-2025-8d1d9dbf02 (zmap-4.3.4-1.el10_1) has been pushed to the Fedora EPEL 10.1 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 17 Fedora Update System 2025-11-18 02:13:57 UTC
FEDORA-EPEL-2025-dbcc451897 (zmap-4.3.4-1.el9) has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.