afpfs-ng failed to build from source in Fedora rawhide/f35 https://koji.fedoraproject.org/koji/taskinfo?taskID=72322107 For details on the mass rebuild see: https://fedoraproject.org/wiki/Fedora_35_Mass_Rebuild Please fix afpfs-ng 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, afpfs-ng will be orphaned. Before branching of Fedora 36, afpfs-ng 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/
Created attachment 1807149 [details] build.log file build.log too big, will only attach last 32768 bytes
Created attachment 1807150 [details] root.log file root.log too big, will only attach last 32768 bytes
Created attachment 1807151 [details] state.log
Dear Maintainer, your package has an open Fails To Build From Source bug for Fedora 35. Action is required from you. If you can fix your package to build, perform a build in koji, and either create an update in bodhi, or close this bug without creating an update, if updating is not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to acknowledge this. If you have already fixed this issue, please close this Bugzilla report. Following the policy for such packages [2], your package will be orphaned if this bug remains in NEW state more than 8 weeks (not sooner than 2021-09-23). A week before the mass branching of Fedora 36 according to the schedule [3], any packages not successfully rebuilt at least on Fedora 34 will be retired regardless of the status of this bug. [1] https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ [2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ [3] https://fedorapeople.org/groups/schedule/f-36/f-36-key-tasks.html
This bug appears to have been reported against 'rawhide' during the Fedora 35 development cycle. Changing version to 35.
+ /usr/lib/rpm/check-rpaths ******************************************************************************* * * WARNING: 'check-rpaths' detected a broken RPATH OR RUNPATH and will cause * 'rpmbuild' to fail. To ignore these errors, you can set the * '$QA_RPATHS' environment variable which is a bitmask allowing the * values below. The current value of QA_RPATHS is 0x0000. * * 0x0001 ... standard RPATHs (e.g. /usr/lib); such RPATHs are a minor * issue but are introducing redundant searchpaths without * providing a benefit. They can also cause errors in multilib * environments. * 0x0002 ... invalid RPATHs; these are RPATHs which are neither absolute * nor relative filenames and can therefore be a SECURITY risk * 0x0004 ... insecure RPATHs; these are relative RPATHs which are a * SECURITY risk * 0x0008 ... the special '$ORIGIN' RPATHs are appearing after other * RPATHs; this is just a minor issue but usually unwanted * 0x0010 ... the RPATH is empty; there is no reason for such RPATHs * and they cause unneeded work while loading libraries * 0x0020 ... an RPATH references '..' of an absolute path; this will break * the functionality when the path before '..' is a symlink * * * Examples: * - to ignore standard and empty RPATHs, execute 'rpmbuild' like * $ QA_RPATHS=$(( 0x0001|0x0010 )) rpmbuild my-package.src.rpm * - to check existing files, set $RPM_BUILD_ROOT and execute check-rpaths like * $ RPM_BUILD_ROOT=<top-dir> /usr/lib/rpm/check-rpaths * ******************************************************************************* ERROR 0001: file '/usr/bin/afpfsd' contains a standard '/usr/lib64' in [/usr/lib64] ERROR 0001: file '/usr/bin/mount_afp' contains a standard '/usr/lib64' in [/usr/lib64] ERROR 0001: file '/usr/bin/afpcmd' contains a standard '/usr/lib64' in [/usr/lib64] ERROR 0001: file '/usr/bin/afpgetstatus' contains a standard '/usr/lib64' in [/usr/lib64] RPM build errors: error: Bad exit status from /var/tmp/rpm-tmp.5fuRPc (%install) Bad exit status from /var/tmp/rpm-tmp.5fuRPc (%install) Child return code was: 1 EXCEPTION: [Error()]
Setting QA_RPATHS to 1 fixed the build problem, but it is probably not the right /usr/lib64 seems to be appropriate dir for the aarch64, but build of x86_64 (with the same dir) ends-up without this error/warning (logs attached)
Created attachment 1842218 [details] build_aarch64.log Build on aarch64 ends-up with: libtool --tag=CC --mode=link gcc ... -o libafpclient.la -rpath /usr/lib64 gcc ... -Wl,--rpath -Wl,/usr/lib64
Created attachment 1842219 [details] build_x86_64.log The x86_64 build ends-up with: ../libtool --tag=CC --mode=link gcc ... libafpclient.la -rpath /usr/lib64 .. but it seems there is no gcc ... -Wl,--rpath generated by the libtool
This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '35'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.