On 27/05/2022 16.22, Andreas Beckmann wrote: > On 27/05/2022 10.59, Paul Gevers wrote: >>> My guess is that apt pinning comes into play here, installing >> >> That aligns with my suspicion that it's related to the mixing of >> unstable and testing. > > Uploaded a first attempt on the fix. Works for me, let's see how ci.d.o > likes it. There are probably still corner cases to be handled ...
Looks not too bad. Current problems: lime-forensics: used dkms-autopkgtest manually, not via Testsuite: autopkgtest-pkg-dkms merge-request !2 (only autopkgtest buggy, module builds fine) r8125: bug #1012014 - r8125: fails to build module for Linux 5.17 (new upstream release available) nvidia-graphics-drivers-tesla-470: fails on ppc64el due to transitive GPL symbol usage, reported upstream nvidia-graphics-drivers-tesla-510: improved version in experimental, but has the same problem on ppc64el as 470 (not yet in sid due to moving a package from nvidia-graphics-drivers to -tesla-510) feel free to temporarily remove from testing Since these bugs (modules failing to build) are already present in testing and only exposed by the new dkms by making the autopkgtest run no longer a no-op, perhaps you could just ignore the failing tests and hint dkms into testing? (-tesla-510 would need some forced hint for reintroduction into testing as well, since I don't think an upstream fix for ppc64el will be available in time when I move nvidia-graphics-drivers from 470 to 510 as default in sid) Andreas
