Le mar. 14 oct. 2025 à 16:59, Santiago Vila <[email protected]> a écrit :
> On Tue, Oct 14, 2025 at 04:54:27PM +0200, Jérémy Lal wrote: > > > > 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. > > > > > > > Careful with emscripten, it's easy to get lost ;) > > > > I'd rather do the fix myself, unless you want to risk spending a lot of > > time on it. > > Ok, feel free. If you manage to fix the build with > DEB_BUILD_OPTIONS=nocheck alone, > I would gladly find all the BD with improper <!nocheck> afterwards > (because I > already wrote a script for that, which takes no human time). > It should work now, you can proceed. (it was actually a simple FTBFS caused by a fix in python3-filelock, that properly removes one of the lock files, that wasn't supposed to be there, ever).
