https://bugs.winehq.org/show_bug.cgi?id=57859
--- Comment #70 from Rosanne DiMesio dimesio@earthlink.net --- (In reply to Tom Maneiro from comment #68)
(In reply to Shmerl from comment #67)
(In reply to Sveinar Søpler from comment #66)
I do however see that the latest 10.2~noble-4 version still adds the following symlinks:
/usr/bin/wine64 -> /opt/wine-staging/bin/wine64 /usr/bin/wine64-preloader -> /opt/wine-staging/bin/wine64-preloader /usr/bin/wine-preloader -> /opt/wine-staging/bin/wine-preloader
For the reference, I don't see any wine64 symlinks in Debian.
Neither I see anything like that here. The only noise I get is during the postinstall phase, where I notice references to no longer existing wine-preloader binaries:
Configurando wine-devel-i386:i386 (10.2~bookworm-4) ... /opt/wine-devel/bin/wine-preloader (No such file or directory) Configurando wine-devel-amd64 (10.2~bookworm-4) ... /opt/wine-devel/bin/wine64-preloader (No such file or directory) Configurando wine-devel (10.2~bookworm-4) ... Configurando winehq-devel (10.2~bookworm-4) ...
...aside of that, seems everything else finally fell into its proper place, so this 4th release should be safe for upgrading.
There are still some things that need to be cleaned up, (some misplaced man pages, too) but nothing that breaks anything, so it can wait for 10.3.