Bug 2384619 - gftp: FTBFS in Fedora rawhide/f43
Summary: gftp: FTBFS in Fedora rawhide/f43
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: gftp
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gwyn Ciesla
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F43FTBFS
TreeView+ depends on / blocked
 
Reported: 2025-07-30 09:03 UTC by Fedora Release Engineering
Modified: 2025-08-05 16:15 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-08-05 16:15:25 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
build.log (12.37 KB, text/plain)
2025-07-30 09:03 UTC, Fedora Release Engineering 		no flags Details
root.log (32.00 KB, text/plain)
2025-07-30 09:03 UTC, Fedora Release Engineering 		no flags Details
state.log (1.62 KB, text/plain)
2025-07-30 09:03 UTC, Fedora Release Engineering 		no flags Details
View All

Description Fedora Release Engineering 2025-07-30 09:03:00 UTC 
gftp failed to build from source in Fedora rawhide/f43

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


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_43_Mass_Rebuild
Please fix gftp 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,
gftp will be orphaned. Before branching of Fedora 44,
gftp 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-07-30 09:03:06 UTC 
Created attachment 2099270 [details]
build.log
Comment 2 Fedora Release Engineering 2025-07-30 09:03:10 UTC 
Created attachment 2099271 [details]
root.log

file root.log too big, will only attach last 32768 bytes
Comment 3 Fedora Release Engineering 2025-07-30 09:03:13 UTC 
Created attachment 2099272 [details]
state.log
Comment 4 Frédéric Bérat 2025-08-05 09:51:13 UTC 
Using `autoreconf -ivf` instead of `./autogen.sh` should fix the issue. Or autogen.sh needs to be updated to run `autopoint --force`.
Comment 5 Gwyn Ciesla 2025-08-05 16:15:25 UTC 
Thank you, the former failed but the latter worked.
Note You need to log in before you can comment on or make changes to this bug.