Control: severity -1 serious
Control: affects -1 + src:wine
Control: block 1124433 by -1
On Sat, 13 Dec 2025 at 15:39:13 +0100, Antoine Le Gonidec wrote:
Since wine 10.0~repack-12 → 10.0~repack-11 upgrade, running dxvk-setup fails
due to a mislocated binary:
$ dxvk-setup install --stable
/usr/bin/dxvk-setup: line 339: /usr/lib/wine/wine64: No such file or directory
installing dxvk-wine32 in the wine prefix...
[1/2] Creating registry override for dxgi
/usr/bin/dxvk-setup: line 169: /usr/lib/wine/wine64: No such file or
directory
I suspect it should no longer use /usr/lib/wine/wine64, but /usr/bin/wine64
instead,
cf. https://bugs.debian.org/1063506
(same for wine32)
This is causing an autopkgtest regression for dxvk with the new wine
version, which in turn prevents the new wine version from migrating to
testing.
wine maintainers: Would it perhaps make sense to reinstate
/usr/lib/wine/wine64 as a symlink to /usr/bin/wine64 until the affected
packages (at least src:dxvk, src:libassuan and src:libgpg-error) have
been fixed? That would allow the new wine version to migrate.
smcv
