On Thu, 01 Jan 2026 at 09:26:54 +0100, Paul Gevers wrote:
Migration status for wine (10.0~repack-11 to 10.0~repack-12): BLOCKED:
Rejected/violates migration policy/introduces a regression
Issues preventing migration:
These were all caused by the removal of paths in /usr/lib/wine that
other packages were relying on.
In the short term, I think it would be pragmatic to reinstate those
paths (symlinks to wine{,64} and wineserver) in at least wine:amd64 and
wine:i386. That would allow the bugs linked below to be downgraded to
non-RC, at least.
In the longer term, it's up to the wine maintainers whether these paths
are an intended interface or not. If it's an intended interface, they
can be kept forever, and the relevant bugs in other packages can just be
closed. If not, then the bugs linked below can be reassigned to the
other package involved, and wine can remove the symlinks after the bugs
are fixed; it would probably be helpful if the wine maintainers could
confirm what the correct/long-term-stable replacements are.
∙ ∙ Autopkgtest for dxvk/2.7.1-2: amd64: Regression ♻ (reference ♻),
arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻)
This is https://bugs.debian.org/1122866
∙ ∙ Autopkgtest for libassuan/3.0.2-2: amd64: Regression ♻ (reference
♻), arm64: Pass, i386: Regression ♻ (reference ♻)
This is https://bugs.debian.org/1127141
∙ ∙ Autopkgtest for libgpg-error/1.58-1: amd64: Regression ♻
(reference ♻), arm64: Pass, i386: Regression ♻ (reference ♻)
This is https://bugs.debian.org/1127142
∙ ∙ Autopkgtest for gnupg2/2.4.8-4: amd64: Pass, arm64: Pass, i386:
Regression ♻ (reference ♻)
This is https://bugs.debian.org/1127144
Thanks,
smcv
