Hi, On 5/18/26 3:06 PM, Santiago Vila wrote:
Can you confirm that the following is ok? - the default sbuild mode for bookworm is the file backend (i.e. the old schroot-based followed by sbuild-createchroot in bookworm) - the default sbuild mode for trixie (and above) is the unshare backend.
For bookworm - but not bookworm-backports - this is correct. Technically the use of the unshare backend is a per-buildd host setting, but all but one (mipsel-conova-02.debian.org - which might have been an oversight) have it set.
I ask because after an archive rebuild I found several packages in bookworm which FTBFS using the file backend but build ok using the unshare backend, at least these five: libbio-db-refseq-perl poetry qtnetworkauth-everywhere-src ruby-fastimage scikit-build (I have not reported any of them yet because I need to understand the issue first). My current theory so far is that those packages try to use the network and they build ok at the time, but now this only works ok if network access is disabled (which happens by default when using the unshare backend, which would explain why using unshare makes those weird build failures to disappear).
Thanks for doing this, we should definitely get FTBFS bugs for them even if they build fine on the buildds.
Kind regards Philipp Kern