Hi, On Thu, 05 Sep 2024 14:13:14 +0100 Tj <tj.iam...@proton.me> wrote: > The package needs updating to the current (2024-09-05) upstream HEAD /and/ > build-testing via sbuild to ensure it builds and tests correctly. > > There are an entire series of TIMEOUT issues in the arm and aarch64 > tests that are fixed by various patches since 1.8.6. > > It is not worth trying to pick out the commits to fix the failures - > I've done that extensively and it is not practical. > > The arm tests failed due to two issues; MMU not being enabled > (commit 5252f4dd236e4) and exception vector table being generated with > Thumb instructions not ARM32 (commit dd711267309fbc3d and > b2d921a71ea011d4c1c) but other commits are needed preceding those. > > With all the arm tests fixed there are 32 failed aarch64 tests and no > idea if other architectures will also have failures. > > Building with latest origin/main all tests pass and package builds > successfully.
thank you and mjt for all the time you've put into figuring out what's going on! Since Keith seems to still be busy, I'm wondering how to best fix this FTBFS via an NMU without doing a huge change like importing a new upstream release. What do you think of doing a minimal NMU which just temporarily (until a new upstream version is packaged) disables the tests? Thanks! cheers, josch
signature.asc
Description: signature
