[pkg-gnupg-maint] Bug#1127141: libassuan: autopkgtest regression with wine/10.0~repack-12

[Simon McVittie]

Source: libassuan,wine
Control: found -1 libassuan/3.0.2-2
Control: found -1 wine/10.0~repack-12
Control: block 1121773 by -1
Severity: serious
Tags: forky sid
Justification: https://release.debian.org/testing/rc_policy.txt 6a
User: debian-ci at lists.debian.org
Usertags: breaks needs-update

Since wine was updated to 10.0~repack-12, it no longer provides 
/usr/lib/wine/wine64. Instead, it's now /usr/bin/wine64 or 
/usr/lib/${DEB_HOST_MULTIARCH}/wine/wine. Similarly, the 
wineserver is now /usr/lib/${DEB_HOST_MULTIARCH}/wine/wineserver.

This breaks assumptions made by the autopkgtest in libassuan, causing 
the new wine version to be unable to migrate to testing, which in turn 
results in #1124433 not getting fixed in testing.

If this is an intentional interface change, then 
debian/tests/build-windows in src:libassuan will need updating to use 
more appropriate paths. Perhaps the Wine maintainers could suggest a 
patch?

Even if this was an intentional interface change, it might be a good 
idea to special-case wine:amd64 and wine:i386 to provide enough symlinks 
in /usr/lib/wine/ that the libassuan test will still pass: that would 
allow this bug to be reassigned to src:libassuan at a lower severity, 
and the compatibility symlinks could be removed when libassuan and other 
affected packages (dxvk, libgpg-error) have been updated.

Or, if this was not an intentional interface change, perhaps wine should 
special-case wine:amd64 and wine:i386 to provide those symlinks in the 
longer term?

I've usertagged this as both "breaks" and "needs-update" because it 
isn't obvious to me whether changes are desired in libassuan, in wine, 
or both, but at least one of these two packages will need changes before 
a version of wine with the new paths can migrate.

Thanks,
    smcv