Package: sbuild Version: 0.87.0 Hi.
Using the latest sbuild, I'm getting this in some failed build logs: Purging /build/reproducible-path Not cleaning session: cloned chroot in use E: 10mount: umount: /run/schroot/mount/trixie-file-c2b83387-2e15-4f1c-b04d-03a1f557313e: target is busy. E: 10mount: rmdir: failed to remove '/var/run/schroot/mount/trixie-file-c2b83387-2e15-4f1c-b04d-03a1f557313e': Device or resource busy E: trixie-file-c2b83387-2e15-4f1c-b04d-03a1f557313e: Chroot setup failed: stage=setup-stop Chroot cleanup failed E: Build failure (dpkg-buildpackage died) This used to happen a long time ago when I was using a mix of chroot backends, including directory-based, overlayfs, and overlayfs + eatmydata. It has not happened ever again (which I know) after I switched to file-based schroot backend. And now apparently it's happening again with the file-based schroot backend. Can you think of a reason why the switch to "/build/reproducible-path" make this more likely to happen? May a process not killed properly from one build affect the next build in the same autobuilder? That would be my main concern. Thanks.
