Hi Steven,

On 2025-04-21 07:19, Steven Robbins wrote:
I am able to reproduce it thanks to NoisyCoil's hint about
--aspcud-criteria. I'm working on a fix now.

Okay, I don't know how to solve this.  The package is uploaded now for
unstable so the --aspcud thing no longer matters.

Using sbuild --dist=sid --chroot-mode=schroot insighttoolkit5_5.4.3-3.dsc, the
package will build seemingly fine.

Using sbuild --dist=sid --chroot-mode=unshare insighttoolkit5_5.4.3-3.dsc, the
errors seen in the buildd logs appear ("error: ‘FFTW_ESTIMATE’ was not
declared in this scope")

Best I can figure is that the sbuild "unshare" mode does something tricky that foils something somewhere. Maybe an include doesn't show up at the right
path?

Santiago Vila did an archive rebuild with the new sbuild version (thank you!!) before we uploaded it to unstable. It's unlikely we introduced new FTBFS bugs with the 0.89.0 upload of sbuild.

I'm interested in getting to the bottom of this, especially if you say that the only difference is in the chroot backend of sbuild. If you would like to talk about this more, please open a bug against sbuild that includes all the information that I need to reproduce your issue.

It would be great if you would be able to come up with a more minimal reproducer than insighttoolkit5. Not only does the package take ages to build, my laptop is an arm64 machine and insighttoolkit5 is limited to amd64 and I cannot run sbuild on the porterboxes. I can run sbuild on amd64 on salsaci but as Otto has pointed out in an earlier message, your package is too large for salsaci. If you could create a more minimal (and maybe even architecture independent?) reproducer that would be very helpful and it might even already give you an idea where the problem is.

I also can't figure out how to examine the chroot after a failure: using "--
purge=successful" doesn't work with unshare.

I usually use --anything-failed-commands=%s which gives you a shell that you can use to investigate the build independent of the chroot backend.

Thanks!

cheers, josch

Reply via email to