Bug 2329938

Summary: ntpsec FTBFS on F42 possibly due to waf upgrade to 2.1.2
Product: [Fedora] Fedora Reporter: Mamoru TASAKA <mtasaka>
Component: ntpsecAssignee: Miroslav Lichvar <mlichvar>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: rawhideCC: geert, igor.raits, mlichvar
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-12-03 14:39:22 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 for x86_64 none

Description Mamoru TASAKA 2024-12-02 14:11:34 UTC
As koschei shows:
https://koschei.fedoraproject.org/package/ntpsec

currently ntpsec FTBFS on rawhide, possibly with waf upgrade to 2.1.2.

ntpsec-1.2.3-7.fc41
waf-2.1.2-1.fc41

Reproducible: Always

Comment 1 Mamoru TASAKA 2024-12-02 14:13:23 UTC
Created attachment 2060822 [details]
build log for x86_64

scratch build:
https://koji.fedoraproject.org/koji/taskinfo?taskID=126461084

Comment 2 Miroslav Lichvar 2024-12-03 12:01:41 UTC
It seems this is due to the optparse->argparse switch in waf-2.1.0.

Upstream request to port to new waf: https://gitlab.com/NTPsec/ntpsec/-/issues/830

Comment 3 Miroslav Lichvar 2024-12-03 13:19:39 UTC
The Fedora package now uses for building the waf included in the ntpsec tarball to avoid this incompatibility.

Thanks for the report.

Comment 4 Mamoru TASAKA 2024-12-03 14:27:08 UTC
Still does not build, now with python issue:
https://koji.fedoraproject.org/koji/taskinfo?taskID=126493237

Would you actually once bump release and do real build on koji/rawhide?

Comment 5 Miroslav Lichvar 2024-12-03 14:39:22 UTC
Should be fixed now.