Hi, I am not able to reproduce the test failure visible at https://buildd.debian.org/status/fetch.php?pkg=insighttoolkit5&arch=amd64&ver=5.4.3-2&stamp=1745014062&raw=0 in a local build myself, so I can't help with that. I did however notice that the size of the resulting packages were quite small 2-6 MB compared to the massive 425 MB source package:
1.7M insighttoolkit5-examples_5.4.3-2_all.deb 24K insighttoolkit5_5.4.3-2.debian.tar.xz 4.0K insighttoolkit5_5.4.3-2.dsc 40M insighttoolkit5_5.4.3-2_amd64.build 28K insighttoolkit5_5.4.3-2_amd64.buildinfo 4.0K insighttoolkit5_5.4.3-2_amd64.changes 425M insighttoolkit5_5.4.3.orig.tar.gz 3.2M libinsighttoolkit5-dev_5.4.3-2_amd64.deb 6.2M libinsighttoolkit5.4_5.4.3-2_amd64.deb In unpacked sources 531 MB is binary blob directory .ExternalData/. This massive source package size is currently making the Salsa CI at https://salsa.debian.org/med-team/insighttoolkit fail, and preventing you from potentially seeing the build failure in Salsa CI before the upload to experimental. It would ideal if you can test the builds with Salsa CI before upload instead of having to rely on the actual Debian archive for testing purposes like you have now with the last couple of uploads in recent days. Have you considered putting .ExternalData/ in debian/copyright Exclude-Files so that the source package in Debian would be without those binary blobs? That might allow you to run Salsa CI without hitting artifact size limits.
