https://bugs.winehq.org/show_bug.cgi?id=57859
Jason van der Waals the.jaysun99@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |the.jaysun99@gmail.com
--- Comment #33 from Jason van der Waals the.jaysun99@gmail.com --- (In reply to vangli@online.no from comment #30)
Hi
As a pure user of wine, I wonder how long time it will take to fix this? For a standard (or non-competent like me) user, this may easily been seen as a blocking bug. The core developer of wine certainly has good reasons for their decisions of the changes introduced. No complains about that.
However, such a "blocking" changes may for the standard user be extreme critical and put some uncertainty about the quality of wine, if it is not fixed very fast (a day or two). For those users of debian based system, could it be possible to release something like a "version 10.2.1.fallback" purely using version 10.1. Following normal updates, this will overwrite the failing 10.2 version following standard updates procedures, thus making wine run-able again.
This may be an idiotic proposal, but....
Bent
Hi, the packages you find here are provided by volunteers, AFAIK creating and maintaining them is not their full-time job. Many projects of this size often don't provide 1st-party, pre-built packages at all - you have build them yourself or rely exclusively on your distro's repositories.
Based on what you wrote, you should probably stick with wine-stable, as wine-devel is under active development and things are known to "break" sometimes. Last stable came out about a month ago, so most features are there. Or alternatively, use the version your distribution provides.