Package: autopkgtest Severity: normal Hello,
The starpu package migration status exposes an interesting issue: https://qa.debian.org/excuses.php?package=starpu The armel and armhf archs get a regression on the eztrace package, for instance on armel: https://ci.debian.net/packages/e/eztrace/testing/armel/44565975/ What happens is that: - the testbed preparation for the first test (command1) installs the non-t64 libraries libevent-core-2.1-7 libevent-pthreads-2.1-7 libopen-trace-format2-10 libopenmpi3 libpmix2 from testing. - Then other tests install other packages from testing. - The last test (command9) is the one that actually tries to install the newer libstarpu-dev library from unstable. autopkgtest first realizes that asking apt to pull only starpu from unstable won't work (since it depends on some other t64 libraries), so it tries again with enabling unstable for all packages: autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from unstable - But apparently apt does not like replacing libevent-core-2.1-7 libevent-pthreads-2.1-7 libopen-trace-format2-10 libopenmpi3 libpmix2 with libevent-core-2.1-7t64 libevent-pthreads-2.1-7t64 libopen-trace-format2-10t64 libopenmpi3t64 libpmix2t64 Then autopkgtest runs apt a last time to get more information: autopkgtest: WARNING: Test dependencies are unsatisfiable - calling apt install on test deps directly for further data about failing dependencies in test logs which does happen to find the expected solution, but autopkgtest stops there. Should we perhaps make autopkgtest really try this last attempt? Samuel
