Hi again, On Fri, Apr 06, 2018 at 09:12:09PM -0700, Steve Langasek wrote:
> In addition to bug #895103, the why3 autopkgtests also fail on non-x86 > architectures in Ubuntu because the test dependencies for the why3+cvc4 test > cannot be satisfied. The attached patch makes the test dependency > architecture-specific and lets it pass as a no-op on architectures without > cvc4. sorry but I do not agree to apply this patch. I don't think that hardcoding in the why3 package the list of architectures on which cvc4 currently builds is the right way to solve this issue. Note that cvc4 is only one in a list of alternative dependencies. This rather looks to me like a missing feature in autopkgtest: we would need a tag in the test control file that states that failure to satisfy the build-dependencies of a test is not to be considered fatal. At the base of this there is an interesting problem with alternative dependencies: if your tool can interact with any of a list of packages than it is sufficient to install one of these to make your tool work. However, one might want to test that your tool interoperates correctly with *all* packages among the alternatives. Cheers -Ralf.
