Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1541105

Summary: flatpak: FTBFS due to incorrect copy_file_range detection
Product: [Fedora] Fedora Reporter: Florian Weimer <fweimer>
Component: flatpakAssignee: David King <amigadave>
Status: CLOSED NEXTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 28CC: amigadave, klember
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: flatpak-0.11.3-1.fc28 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-02-24 22:01:00 UTC Type: Bug
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: 1539083    

Description Florian Weimer 2018-02-01 17:17:36 UTC
libglnx/libglnx.m4 does not list copy_file_range in AC_CHECK_DECLS, so the HAVE_DECL_COPY_FILE_RANGE preprocessor macro is never defined, and the syscall wrapper detection in libglnx/glnx-missing-syscall.h does not work.

This has been “fixed” by tagging the Fedora 27 build into the Fedora 28 buildroot, but this build does not use the correct Fedora build flags.

Comment 1 Kalev Lember 2018-02-07 09:11:34 UTC
Thanks, should be fixed by https://github.com/flatpak/flatpak/pull/1389

Comment 2 Fedora End Of Life 2018-02-20 15:30:49 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle.
Changing version to '28'.

Comment 3 Florian Weimer 2018-02-24 22:01:00 UTC
Confirmed as fixed in flatpak-0.11.3-1.fc28.