Hi Paul
On 09.03.23 15:50, Paul Gevers wrote:
Hi,
On Sun, 19 Feb 2023 18:17:39 -0600 Austin English
<austinengl...@gmail.com> wrote:
Yes, it's arguably a bug in winetricks. Film what I gather upstream,
it's also not yet fully supported.
On Sat, 25 Feb 2023 17:10:47 +0100 Jens Reyer <jre.wine...@gmail.com>
wrote:
ftr: I just uploaded a new winetricks 20230212-1 to unstable which
should migrate to bookworm before the hard freeze. It workarounds a
missing /usr/bin/wine64. The fix is quite late in Winetricks logic to
figure out wine64, so it should work just fine with both setups.
Tested against wine 8.0~repack-2, 8.0~repack-4 and winehq-staging
8.2~bookworm-1.
If I understand correctly, this bug can now be downgraded in severity
because winetricks migrated to bookworm. Maybe even better, reassign to
winetricks and close it with the version in bookworm? Or am I missing
the point?
Well, yes, from my winetricks perspective this bug could be closed as
described.
But I suspect (without any evidence) that a missing /usr/bin/wine64 also
affects others, at least in non-packaged software, but maybe also in
Debian. Changing this now shortly before the release imo calls for
trouble. In general I think /usr/bin/wine64 should be kept as long as
Wine is built as it is now, since just too many people got used to it.
Only once Wine is built the new way (upstream is still working on this)
this setup should be changed.
This change was intended to fix #1029536, where I unfortunately
mentioned that removing /usr/bin/wine64 might solve the issue. That
issue may be either ignored or preferably fixed another way, e.g. by
doing a "ln -s /usr/lib/wine/wine64 /usr/lib/wine/wine64-stable".
Finally this issue here blocked the fix for #1031102 from migrating to
testing. As far as I see that could be ignored, since it's a build
issue with vulkan 1.3.239, which is also only in unstable. I do not know
if the current wine 8.0~repack-4 would even build with the vulkan
currently in testing. If it doesn't there would be a new rc bug.
So we have three options (ordered best to least from my perspective, and
assuming wine builds with both vulkan versions from testing and unstable
(requirement for 1 and 3). Please note that I stepped down from
maintaining wine, and might miss something).
1.
Revert the /usr/bin/wine64 removal, add the /usr/lib/wine/wine64-stable
link instead, and then let wine migrate to bullseye.
2.
Keep everything as it is now, make sure vulkan 1.3.239 doesn't make it
to bullseye, and bullseye-ignore this and the 2 other bugs.
3.
Reassign this bug as you suggested to winetricks and close it with the
version in bookworm.
Greets
jre
