Source: gsocket Version: 1.4.43-1 Severity: important Tags: FTBFS, patch User: debian-ri...@lists.debian.org Usertags: riscv64 X-Debbugs-Cc: debian-ri...@lists.debian.org
Dear gsocket Maintainer, The gsocket package build failed on riscv64 caused by symbol diff.The crucial buildd log below: ``` dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/gsocket/DEBIAN/symbols doesn't match completely debian/gsocket.symbols --- debian/gsocket.symbols (gsocket_1.4.43-1_riscv64) +++ dpkg-gensymbolshgJ2V_ 2024-05-25 03:27:13.445566913 +0000 @@ -17,10 +17,10 @@ thc_gethostbyname@Base 1.4.39 thc_hostname@Base 1.4.39 gsocket_uchroot_dso.so.0 gsocket #MINVER# - (arch=!i386 !amd64 !arm64)__lstat64_time64@Base 1.4.43 +#MISSING: 1.4.43-1# (arch=!i386 !amd64 !arm64)__lstat64_time64@Base 1.4.43 __lxstat64@Base 1.4.39 __lxstat@Base 1.4.39 - (arch=!i386 !amd64 !arm64)__stat64_time64@Base 1.4.43 +#MISSING: 1.4.43-1# (arch=!i386 !amd64 !arm64)__stat64_time64@Base 1.4.43 __xstat64@Base 1.4.39 __xstat@Base 1.4.39 chmod@Base 1.4.39 dh_makeshlibs: error: failing due to earlier errors make: *** [debian/rules:6: binary-arch] Error 25 dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2 ``` The full buildd log is here: https://buildd.debian.org/status/fetch.php?pkg=gsocket&arch=riscv64&ver=1.4.43-1&stamp=1716607641&raw=0 My solution to this issue: Similar to the solution on amd64, ignore related symbol on riscv64.I have tested this modification in local, and it works well. Please let me know wheather this solution can be accepted. Gui-Yue Best Regards
fix_symbol_on_riscv64.patch
Description: Binary data