[Bug 56218] New: [macOS] [10.14] Last release of wine-stable via Homebrew doesn't work on macOS 10.14
https://bugs.winehq.org/show_bug.cgi?id=56218
Bug ID: 56218 Summary: [macOS] [10.14] Last release of wine-stable via Homebrew doesn't work on macOS 10.14 Product: Wine Version: 9.0-rc5 Hardware: x86-64 OS: MacOS Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: mestesso.me@virgilio.it
Updating wine-stable package via-Homebrew on macOS 10.14 makes Wine un-usable.. It says that macOS 10.15 is required!
Remember that 10.14 is both x86 and x64 system, and many of us can't upgrade to 10.15.. Please, keep (or revert) version for macOS 10.14 too
https://bugs.winehq.org/show_bug.cgi?id=56218
Gcenx gcenx83@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |gcenx83@gmail.com
--- Comment #1 from Gcenx gcenx83@gmail.com --- (In reply to mestesso.me from comment #0)
Updating wine-stable package via-Homebrew on macOS 10.14 makes Wine un-usable.. It says that macOS 10.15 is required!
Who ever updated the cask should have added depends_on catalina, I’ve already open a PR to reflect this new requirement with these packages.
(In reply to mestesso.me from comment #0)
Remember that 10.14 is both x86 and x64 system, and many of us can't upgrade to 10.15..
As I no longer have a functional Intel Mac it’s harder to provide functional packages.
The easiest option would have been make use of prebuilt libraries from Macports, but the wine package maintainer hasn’t updated it in years so there’s no longer any prebuilt universal libraries required for modern wine.
(In reply to mestesso.me from comment #0)
Please, keep (or revert) version for macOS 10.14 too
That’s up-to brew if they’d like to handle this, but as brew only supports macOS versions supported by Apple I doubt they’d consider doing this.
Current alternative solutions are: - Use my macports overlay https://github.com/Gcenx/macports-wine - Download the older wine-stable https://github.com/Gcenx/macOS_Wine_builds/releases/tag/8.0.1
https://bugs.winehq.org/show_bug.cgi?id=56218
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTOURBUG
--- Comment #2 from Austin English austinenglish@gmail.com --- This should be reported to Homebrew; it's not a Wine bug.
https://bugs.winehq.org/show_bug.cgi?id=56218
--- Comment #3 from Gcenx gcenx83@gmail.com --- (In reply to Austin English from comment #2)
This should be reported to Homebrew; it's not a Wine bug.
https://github.com/Homebrew/homebrew-cask/pull/164874
https://bugs.winehq.org/show_bug.cgi?id=56218
mestesso.me@virgilio.it changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|NOTOURBUG |--- Status|RESOLVED |UNCONFIRMED
--- Comment #4 from mestesso.me@virgilio.it --- Not yet solved.
It is a Wine Bug! Homebrew only delivers what Wine puts in!
So.. The solution adopted by others is to keep old version available, like “wine-stable@8.21” or “wine-stable@9.0-rc5”, and not only latest “wine-stable”.
That’s possible, why not using that possibility?!? Packages are on github, so..
https://bugs.winehq.org/show_bug.cgi?id=56218
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |NOTOURBUG Status|UNCONFIRMED |RESOLVED
--- Comment #5 from Alexandre Julliard julliard@winehq.org --- It is a Homebrew bug, they are the ones who decide how they build it.
https://bugs.winehq.org/show_bug.cgi?id=56218
--- Comment #6 from Gcenx gcenx83@gmail.com --- (In reply to mestesso.me from comment #4)
Not yet solved.
brew officially supports macOS Monterey and later (as of Jan 22nd 2024)
(In reply to mestesso.me from comment #4)
It is a Wine Bug! Homebrew only delivers what Wine puts in!
You didn’t read me message at all, I no longer own a functional Intel Mac so I can’t build for these legacy targets.
(In reply to mestesso.me from comment #4)
So.. The solution adopted by others is to keep old version available, like “wine-stable@8.21” or “wine-stable@9.0-rc5”, and not only latest “wine-stable”.
That’s possible, why not using that possibility?!? Packages are on github, so..
Again brew only officially supports macOS Monterey and greater, if brew wants to add a fallback for these legacy platforms that’s upto brew.
However even if they’re somehow convinced we’ll no longer take bug for these legacy versions of wine.
Again I personally can’t provide packages for legacy versions of macOS as I no longer own an Intel Mac that’s capable of running said legacy versions of macOS.
Unless someone wants to ether donate me a system that’s capable of running legacy version of macOS or wants to provide package for these legacy macOS versions there’s nothing I can do.
If you read my message again I do provide a macports overlay to assist in holding wine on macOS, upstream macports wine package maintainer hasn’t updated the packages in years and shows no interest nor desire to do so anymore. All my attempts to get fixes into macports for building +universal on macOS Mojave ware shot down and I’m not allowed to take over the wine ports.
-
WineHQ Bugzilla