LinuxMusicians

Hello,

I think carla-bridge-wine32:i386 is broken with the last wine release (5.0~rc1-1 on Debian unstable). Plugins just do not work anymore and a new scan doesn't find them at all).
A rollback to wine32=4.0.3-* fixes the problem.

So if you're on unstable, apt-pinning is your friend until this is resolved

gelabs wrote:https://bugs.debian.org/cgi-bin/bugrepo ... bug=946951

Bloody hell. I took a look at that bug report. Quote:

Actually, the program does not matter. The error seems to occur very
early, before wine tries to look at the program:

$ wine zzzzzzzzzz
wine: chdir to /run/user/1000/wine/server-805-14c0be6 : No such file or directory

This means that the developers made their "all new and improved" version of Wine world-wide available without testing it with even one single Windows executable. And the thing Wine does is ... running Windows executables. This worries me very much. I can appreciate that parts of the Linux ecosystem are made by volunteers in their free time, but this extreme form of unprofessionalism is unacceptable. Just keep yer bloody stinkin' paws of of source code if you are incompetent and not able to do even the very least of testing. If it an't broke, don't try to fix it!

it's a RC -> release candidate
the purpose it to find bugs
if you are using release candidates on a production system , you're doing it wrong

so calm down

rghvdberg wrote:it's a RC -> release candidate
the purpose it to find bugs
if you are using release candidates on a production system , you're doing it wrong

so calm down

So this package is part of Debian Sid Unstable? Or is it part of Debian Testing, on which Ubuntu etc. is based? I can appreciate RC's are there to find bugs, but not testing a new Wine version with even one singe Windows executable? Isn't that unprofessional?

There's a big red balloon on that page which says "unstable"
and you don't know if they didn't test it.
Maybe it worked on the distro the devs used it, you never know what happened.
My bet it's something that sneaked in at the last minute. Some small edit or a failed merge or something that somehow borked things.

Yes, that was for unstable.
The bug has been fixed on version 5.0~rc1-2, so everything's fine again.

gelabs wrote:Yes, that was for unstable.
The bug has been fixed on version 5.0~rc1-2, so everything's fine again.

Thanks for the info. I learned a lesson here (always ask if somebody is using a "testing" branch).