Hi,
On 2025-04-20 15:12, Santiago Vila wrote:
Hi. After a few more tests, I really think this is a problem in
sbuild which is already fixed in git.
The exact nature I can't determine, but the problem only happens
when using sbuild 0.89.0 with the file backend (i.e. schroot).
When I use sbuild 0.89.0 + pending commits, the problem seems
to go away.
I find it very unlikely that the two commits which currently sit in
"main" on top of what is in unstable are fixing any FTBFS.
One commit fixes a bug of the last upload which prevented a user from
specifying an empty (i.e. random) build path.
The other commit fixes a bug which would let sbuild fail to start with
the unshare backend when run in an environment (like docker) where
/dev/console does not exist.
Is the test maybe a bit flaky?
Thanks!
cheers, josch
