Hi

mingw-qt5-qtbase and mingw-qt5-qttools are currently FTBFS [1] due to errors like


error: Could not open %files file 
/builddir/build/BUILD/qtbase-opensource-src-5.9.1/debugsourcefiles.list: No 
such file or directory
    Duplicate build-ids 
/builddir/build/BUILDROOT/mingw-qt5-qtbase-5.9.1-4.fc27.x86_64/usr/i686-w64-mingw32/lib/libQt5Bootstrap.so.5.9.1
 and 
/builddir/build/BUILDROOT/mingw-qt5-qtbase-5.9.1-4.fc27.x86_64/usr/x86_64-w64-mingw32/lib/libQt5Bootstrap.so.5.9.1
    Duplicate build-ids 
/builddir/build/BUILDROOT/mingw-qt5-qtbase-5.9.1-4.fc27.x86_64/usr/i686-w64-mingw32/lib/libQt5BootstrapDBus.so.5.9.1
 and 
/builddir/build/BUILDROOT/mingw-qt5-qtbase-5.9.1-4.fc27.x86_64/usr/x86_64-w64-mingw32/lib/libQt5BootstrapDBus.so.5.9.1
    Could not open %files file 
/builddir/build/BUILD/qtbase-opensource-src-5.9.1/debugsourcefiles.list: No 
such file or directory

Indeed, these packages need special logic to deal with debuginfo files because 
both host as well as target binaries are produced by the package, the result up 
to now being

mingw-qt5-qtbase-debuginfo -> host
mingw32-qt5-qtbase-debuginfo -> target
mingw64-qt5-qtbase-debuginfo -> target

This was handled in the spec file [2] as

# Override the __debug_install_post argument as this package
# contains both native as well as cross compiled binaries
%global __debug_install_post %%{mingw_debug_install_post}; 
%{_rpmconfigdir}/find-debuginfo.sh 
%{?_missing_build_ids_terminate_build:--strict-build-id} %{?_find_debuginfo_opts} 
"%{_builddir}/%%{?buildsubdir}" %{nil}


Long text short question: can someone help me adapt this logic for the new 
debuginfo/debugsource mechanism?

Thanks
Sandro

[1] 
https://koji.fedoraproject.org/koji/getfile?taskID=21030286&volume=DEFAULT&name=build.log&offset=-40000
[2] 
https://src.fedoraproject.org/rpms/mingw-qt5-qtbase/blob/master/f/mingw-qt5-qtbase.spec

_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Reply via email to