owner 1116732 ! thanks I will try to fix this as well.
It is possible that the package also fails when built with DEB_BUILD_OPTIONS=nocheck alone, in this way: dh_fixperms debian/rules execute_after_dh_fixperms make[1]: Entering directory '/build/reproducible-path/emscripten-3.1.69+dfsg' chmod -x debian/emscripten/usr/share/emscripten/cache/cache.lock debian/emscripten/usr/share/emscripten/system/lib/lib cxx/readme.txt debian/emscripten/usr/share/emscripten/test/other/wasm_sourcemap/foo.wasm debian/emscripten/usr/share/e mscripten/test/other/wasm_sourcemap_dead/t.wasm debian/emscripten/usr/share/emscripten/tools/system_libs.py debian/ems cripten/usr/share/emscripten/cache/symbol_lists.lock chmod: cannot access 'debian/emscripten/usr/share/emscripten/cache/symbol_lists.lock': No such file or directory make[1]: *** [debian/rules:317: execute_after_dh_fixperms] Error 1 make[1]: Leaving directory '/build/reproducible-path/emscripten-3.1.69+dfsg' make: *** [debian/rules:360: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 So, I guess we should fix that first (help welcome). After that, I can use a script to determine which one of the BD should not have the <!nocheck> annotation. Based on the original build log: embuilder: warning: cannot check node version: [Errno 2] No such file or directory: 'node' [-Wversion-check] embuilder: error: clang executable not found at `/usr/bin/clang-19` make[1]: *** [debian/rules:199: override_dh_auto_build] Error 1 make[1]: Leaving directory '/<<PKGBUILDDIR>>' it looks like "nodejs" and clang-19 would be good candidates, but there may be others. I would let the script to find out. Thanks.
