-
-
Notifications
You must be signed in to change notification settings - Fork 108
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
Errno::ENOENT on install with Ruby 3.2 #199
Comments
still broken with the released Ruby 3.2.0 |
This seems to be an issue with I tested this fix: #200 as well as this fix: #201 and both seem to work. Seems like it's related to this change: rubygems/rubygems#6025. @nickcharlton thoughts? |
I've merged in #202, could someone try with that and see if it's still an issue? |
@nickcharlton just tested it and it worked for me. Thanks! |
@nickcharlton works fine for me. tested with Ruby 2.7, 3.0, 3.1 and 3.2. |
Great, thanks for letting me know! I'm going to close this now but we'll add Ruby 3.2 to CI soon. |
Any chance we can get a release that includes this fix soon? It would fix a number of GitHub Actions CI pipelines that are currently broken. |
It won't be long — I'd like to resolve #188 first, which I have in progress currently. In the short-term, you could do something like: thoughtbot/administrate#1932 and pin against |
unpinned `appraisal` because of an issue with ruby 3.2 + bundler 2.4<=; see thoughtbot/appraisal#199 (comment) unpinning gives us `appraisal 2.5.0`, version by which we have a fix (we want to run `be appraisal install`) to generate lockfiles
Actual
It's interesting to note that
The Gemfile's dependencies are satisfied
is printed, but not accurate, since the example gemos
is not installed yet.Expected
Running with
docker run --rm -it ruby:3.1.3-slim-bullseye /bin/bash
I get:The text was updated successfully, but these errors were encountered: