Hi, I recently uploaded a package to experimental and was suprised at the build failures [1]. I have built it locally and on a porter box without issue -- each time using a clean unstable chroot.
[1] https://buildd.debian.org/status/fetch.php? pkg=insighttoolkit5&arch=amd64&ver=5.4.3-2&stamp=1745014062&raw=0 I am trying to run sbuild in an attempt to reproduce the precise environment. I am using this invocation: sbuild --purge=successful --dist=experimental --build-dep-resolver=aspcud insighttoolkit5_5.4.3-2.dsc However, this also succeeds locally. So clearly I'm not reproducing exactly the buildd environment. I have asked both google and chatgpt but haven't yet been able to uncover exactly what options are used on the buildd. Anyone know how to find this? Comparing the logs, I can see a couple differences: Buildd uses sbuild 0.88.4~bpo12+2 whereas I have 0.89.0. Buildd sets Build Type: any, whereas mine is binary. Beyond that, there's a bunch of packages installed that I haven't waded through yet, but it's tough to believe package versions matter. Except perhaps for fftw, which contains the header where the error occurs. All fftw packages are the same version in both buildd and local. Any help appreciated, -Steve
signature.asc
Description: This is a digitally signed message part.
