https://bugs.winehq.org/show_bug.cgi?id=57859
--- Comment #73 from Tom Maneiro tomman@gmail.com --- (In reply to Sveinar Søpler from comment #72)
(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.
That "noise" is the .deb packages trying to symlink non-existing binaries afaik.
Have you done a "sudo updatedb & locate wine64" and check that you dont have those symlinks in /usr/bin, /bin or /sbin or whatever system folder Debian puts stuff in?
Indeed, such a check tells me that both "wine64/wine64-preloader" symlinks exist at /usr/bin/, and furthermore a query via dpkg -S confirms they both were put there by... winehq-devel. Same deal with wine-preloader (which no longer lives at /opt/wine-devel/bin), and whose /usr/bin/ symlink is also put there by winehq-devel.
So add that to the cleanup tasks for the packaging files then.