Hi, Quoting Matthias Klose (2024-12-03 18:33:14) > > This is because cross-building in unstable from amd64 (build) to arm64 > > (host) is broken right now. The autopkgtest will pass once that is fixed > > in the relevant packages. > > > > Feel free to reassign this bug to the actual culprit, but it is not > > sbuild. > well, there's also gcc-snapshot/gcc-14/gcc-13 failing in the testsuite with > that sbuild upload. So if sbuild is that unreliable, and hinders the > toolchain packages to migrate to testing, then it's probably not a good idea > to test for cross building.
the intention was to let packages migrate once cross building works. The autopkgtest is doing that reliably as opposed to being flaky, no? I thought we had agreed that it is a good idea to do that sort of test. What changed? > PS: and no need for that kind of sarcasm. Which thing I said did you perceive as being sarcastic? The bit about re-assigning the bug? I was not trying to be sarcastic. I believe the bug is not in sbuild. I think that the cross-build test fails because of other packages. For example, I still see that gcc-14 has not built successfully on amd64. But I do not know the details. You probably know them better than I. Thus, I suggested you reassign the bug if you think it to be appropriate. Thanks! cheers, josch
signature.asc
Description: signature
