-
Notifications
You must be signed in to change notification settings - Fork 549
compatibility problem with latest ruby 2.6 #1021
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
Comments
Known issue. Will include Ruby 2.6 for Windows builds in the next release. |
Thanks. Is there any timeline for next release ? |
+1 any estimate? as I am in the middle of planning/executing an upgrade |
Is there any further updates to this or any known workaround in order to have this working in Windows 10 (64Bit) ? |
any update on this? |
Also having this problem.
|
when is the next release? |
ERROR: Error installing mysql2:
The last version of mysql2 (= 0.5.2) to support your Ruby & RubyGems was 0.5.2.
Try installing it with `gem install mysql2 -v 0.5.2`
mysql2 requires Ruby version >= 2.0, < 2.6. The current ruby version is 2.6.3.62. When is the next release come? Environment
|
I'm also very interested in the timeline on this release. |
I'm also keenly interested in the resolution of this incompatibility with Ruby 2.6; our test automation framework is effectively locked into a deprecated version of Ruby (2.3) until mysql2 is updated. |
Does anyone know when is the next release? |
Any furthur news about this? |
I met the same problem. |
Does anyone know when is the next release? |
...when I cut the release. Sorry for the ambiguity and delay, gotta make time for this. |
Please try to do it earliest. |
Please create a fix or a suggest a workaround at the earliest. |
Workaround: manually download the .gem file then install it:
This issue might be caused by releasing multiple |
Hi @sodabrew 👋🏼. First, thank you for all the work needed to maintain and release Rails master (6.1.alpha) recently updated it's Gemfile to require This also affects us at GitHub because we experience this failure as part of our update process for testing against Rails master. Although there are some short-term workarounds, this issue is preventing our update processes from working correctly. Anything you might be able to do to expedite this update and increase the windows ruby version requirement would be greatly appreciated at GitHub and, I'm sure, by the Rails community as a whole. Thanks! |
We also can't get our rails 6 project working without the proper fix released. |
Hi @sodabrew, If you have no time for the new release maybe Rails developers team should pick this up? The plug-in actually important for Rails 6 and mysql compatibility. Many people are using mysql. It is actually baffling why such plugins are actually not part of Rails. Rails require databases to run, strange approach to be honest. |
Awaiting a solution |
Awaiting a solution... |
Anything? |
So I downloaded the gem manually and installed it...and then when I ran
I looked through the bundle documentation and I didn't see a way to request that -- FYI to any Windows-based developers out there: because of this issue, I'm trying out uru to switch between installed ruby versions. I installed uru using the scoop method -- and installed ruby versions using scoop (tip: the dash at the end is essential when specifying a ruby version to install:
|
https://rubygems.org/gems/mysql2 0.5.3 is now posted with updated Windows pre-built binaries for Ruby 2.2 - 2.6. |
sodabrew - newbie here- what exactly do I do to access https://rubygems.org/gems/mysql2 0.5.3? |
Please disregard. I had a "d'uh" moment! I fixed it. |
Hello,
It seems that the new version of mysql2 (0.5.3) donc really work with ruby v2.7 RubyGems Environment:
|
bundle install --force
Fetching gem metadata from https://rubygems.org/..........
Fetching gem metadata from https://rubygems.org/.
Resolving dependencies...
mysql2-0.5.2-x64-mingw32 requires ruby version >= 2.0, < 2.6, which is
incompatible with the current version, ruby 2.6.0p0
The text was updated successfully, but these errors were encountered: