Source: dxvk
Version: 2.7.1-3
Severity: important
https://tracker.debian.org/pkg/dxvk says, among other things:
Issues preventing migration:
∙ Autopkgtest for dxvk/2.7.1-3: [...] loong64: Failed, ppc64el: Failed,
riscv64: Failed, s390x: Failed
This appears to be because the Wine parts of dxvk are uninstallable on
these architectures, so the check-dxvk-setup test-case fails. That's to
be expected, because Wine doesn't support these architectures either.
I suggest the attached patch (untested, but I'm fairly sure it's correct).
The other half of the autopkgtest (the libdxvk-native-dev test-case)
is passing on all supported architectures, so it can stay.
Thanks,
smcv
From: Simon McVittie <[email protected]>
Date: Thu, 16 Jul 2026 16:07:13 +0100
Subject: d/tests/control: Only run check-dxvk-setup on supported
architectures
dxvk Depends on dxvk-wine64 or dxvk-wine32, but dxvk-wine64 is only
available on amd64 and arm64, and similarly dxvk-wine32 is only available
on i386 and armf. wine is also limited to those four architectures.
Don't attempt to run this test on other architectures, like s390x:
anything involving Wine is not going to be useful there.
libdxvk-native-dev and the libraries that it depends on will continue
to be built and tested on non-Wine architectures.
Closes: #-1
Signed-off-by: Simon McVittie <[email protected]>
---
debian/tests/control | 1 +
1 file changed, 1 insertion(+)
diff --git a/debian/tests/control b/debian/tests/control
index c472228f0..8990623a8 100644
--- a/debian/tests/control
+++ b/debian/tests/control
@@ -1,4 +1,5 @@
Tests: check-dxvk-setup
+Architecture: amd64 arm64 i386 armhf
# cross-test-friendly autopkgtest deps
# see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005883
# TODO: remove dpkg-dev when a real solution for wineserver is found
