-
-
Notifications
You must be signed in to change notification settings - Fork 12.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mysql-client: fix add authentication plugins in [email protected] #181805
Conversation
297f0cb
to
ba8b9c8
Compare
This adds the `-DWITH_AUTHENTICATION_CLIENT_PLUGINS=yes` flag to add support for older MySQL authentication methods. This support was in the default build prior to MySQL 9.0, but were dropped with that release. Closes Homebrew#180498
ba8b9c8
to
0dc3ffd
Compare
Can you make an issue upstream requesting they enable this by default and add that as a comment? From the linked thread it seems like upstream thinks it's default already. |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
@SMillerDev I downloaded the MySQL Community Server 9.0.1 Innovation on macOS from https://dev.mysql.com/downloads/mysql/5.5.html?os=31&version=5.1, it gets
|
should reopen this merge request? |
If Oracle made it the default there is nothing for Homebrew to change. If they didn't, someone should make an issue about it on their side before we re-open anything. |
Filed bug upstream: https://bugs.mysql.com/bug.php?id=116616&thanks=4 To note, the quoted documentation in #180498 is from the MySQL 9.0 server release notes, which are likely not treated as "official" documentation by upstream. |
@SMillerDev – Now that Oracle's MySQL support team has verified and agreed with the bug @cswingler opened, can we please reconsider accepting this patch? I understand Homebrew doesn't want to be in the business of modifying default build config, and you're absolutely correct that the root fix is upstream. However, this issue is affecting a lot of customers and it seems worth patching quickly in Homebrew, in addition to fixing in upstream. Could we please consider an exception since this is the second most upvoted issue in the Homebrew repository? There is strong evidence that this was an accident by Oracle and will eventually be fixed upstream:
We're seeing customer issue reports from Homebrew customers for our product and I know it would help a lot of other Homebrew customers to accept this patch, instead of waiting for Oracle's much slower release cycle. Thank you for considering this! 🙏 We are very appreciative of all the work Homebrew maintainers do and I know accepting a build config patch should not be done lightly. |
@fulghum I'm happy to review a PR like this one with a link to the upstream bug report. |
Thank you @SMillerDev!!! 🙏 Are you able to reopen this PR if @cswingler updates the description to include the link to the accepted upstream bug report? Or would you prefer we open a new/fresh PR with this change? Thank you for considering an exception here! |
I've modified the description to add the bug report as a link. @SMillerDev can you reopen this PR, or should I just go ahead and submit a new one? |
I can't reopen it. You'll have to make a new one. |
Thank you @SMillerDev! I've opened up a PR (#201679) that applies the fix to the |
HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>
, where<formula>
is the name of the formula you're submitting?brew test <formula>
, where<formula>
is the name of the formula you're submitting?brew audit --strict <formula>
(after doingHOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>
)? If this is a new formula, does it passbrew audit --new <formula>
?This addresses #180498 .
The MySQL 9.0 client is not built with support for older authentication methods by default, which breaks the ability for the MySQL client, and packages that depend on it, to connect to servers still using authentication methods like
mysql_native_password
. This adjusts the build process to add those back in as plugins.A bug has been opened upstream to address the discrepancy between the documentation and the actual configuration: https://bugs.mysql.com/bug.php?id=116616