Source: fcitx5-m17n Version: 5.1.2-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250124 ftbfs-trixie
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory > '/build/reproducible-path/fcitx5-m17n-5.1.2/obj-x86_64-linux-gnu' > cd /build/reproducible-path/fcitx5-m17n-5.1.2/obj-x86_64-linux-gnu/test/addon > && /usr/bin/cmake -E copy > /build/reproducible-path/fcitx5-m17n-5.1.2/obj-x86_64-linux-gnu/im/m17n.conf > /build/reproducible-path/fcitx5-m17n-5.1.2/obj-x86_64-linux-gnu/test/addon/m17n.conf > [ 84%] Built target fcitx5-m17n-translation > make[3]: Leaving directory > '/build/reproducible-path/fcitx5-m17n-5.1.2/obj-x86_64-linux-gnu' > [ 84%] Built target copy-addon > /build/reproducible-path/fcitx5-m17n-5.1.2/im/overrideparser.cpp: In function > ‘std::vector<OverrideItem> ParseDefaultSettings(FILE*)’: > /build/reproducible-path/fcitx5-m17n-5.1.2/im/overrideparser.cpp:48:10: > error: ‘stable_sort’ is not a member of ‘std’ > 48 | std::stable_sort(list.begin(), list.end(), > | ^~~~~~~~~~~ > make[3]: *** [im/CMakeFiles/m17n.dir/build.make:96: > im/CMakeFiles/m17n.dir/overrideparser.cpp.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2025/01/24/fcitx5-m17n_5.1.2-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20250124;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20250124&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
