I am generally unfamiliar with some of these _javascript_ packages, although my intention is to replace any system copies that exist. I see that you have filed a similar bug with qt6-webengine, although Patrick considers it to be a false positive.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023333
My guess is that whatever rollup code exists in Qt WebEngine is inherited from Chromium, but I don’t see a bug report there.
Can you please explain the procedure you used to try to build qtwebengine-opensource-src (qt5-webengine) with the system rollover and how it failed?
I see that the current package (5.15.13+dfsg-4) build depends on the current versions of rollup and node-rollup-plugin-terser, but that doesn’t necessarily mean that they are being used instead of an embedded copy. It appears that we might be currently, unintentionally shipping an embedded copy in:
./src/3rdparty/chromium/third_party/devtools-frontend/src/node_modules/rollup
Any help you can provide to point us in the right direction would be appreciated.
Thanks,
Soren
--
Soren Stoutner
soren@stoutner.com
Attachment:
signature.asc
Description: This is a digitally signed message part.