When a package fails to build with the nocheck build profile, one
common reason is that some of the build-dependencies marked <!nocheck>
should really not have such annotation.

The present script can help you to determine which ones of those
build-dependencies should not have the <!nocheck> annotation.

To use it, create a file called package.txt with the build-dependencies
you want to check, one per line, where "package" is the name of the
package, like this:

binaryen
clang-19
cmake
dh-nodejs
esbuild
fonts-liberation
lld-19
llvm-19
node-acorn
nodejs
node-source-map
python3-numpy
python3-ply
scons
wabt

Adjust the sbuild command line so that it works in your case, then issue the following command

check-nocheck package.txt

The script will take the package name by removing the ".txt" part,
then will try to build the package with all the build-dependencies,
and then dropping one build-dependency at a time.

You can see the progress by doing this in another terminal:

tail -f package.log

as that's the file where the script will write what it does, and what it finds.

At the end, the script will log in this logfile the build-dependencies
that should not have the <!nocheck> annotation.