On Thu, Oct 17, 2024 at 10:20:04PM +0200, gregor herrmann wrote: > What seems to be happening here is that the first two are not yet > installable in testing (arch:any packages which are part of the > transition and haven't migrated yet), [0] so the third one -- > libuuid-tiny-perl -- > gets installed which causes this warning. [1]
Yes, I agree. Choosing the alternative that causes a warning is a result of autopkgtest package pinning here and doesn't happen usually. > All going as planned, just that we are running into some corner case > of the Debian machinery (testing migration during transitions vs. > autopkgtests with a mixture of testing and unstable and different > dependency resolution [1]). I do wonder if we're testing the right thing in the autopkgtest checks at the moment. If a test doesn't pass with some permutation of the alternative dependencies, either the test dependencies or the test itself seem buggy to me. I'm tempted to say we should only Depend on those alternatives that don't cause a warning. Another possibility would be to allowlist the warning so the autopkgtest check wouldn't fail. -- Niko
