-
-
Notifications
You must be signed in to change notification settings - Fork 2k
Could not find minitest-4.7.5.gem for installation #2854
Comments
Thank you for reporting this. Can you please supply all of the information requested in ISSUES so that we can try to diagnose the problem? Thanks! |
I use the commands "bundle package" / "bundle install --local --path vendor/bundle" for install my gems, but this error always happen: "Could not find minitest-4.7.5.gem for installation". Bundle env results: Bundler 1.5.2 Bundler settings Gemfile gem 'rails', '4.0.2' gem 'mysql2' gem 'sass-rails', ' gem 'jquery-rails' gem 'turbolinks' Gemfile.lock PLATFORMS DEPENDENCIES |
I am also having this exact same issue. |
I'm reverting the change that caused this problem and releasing 1.5.3 today. If that doesn't fix your issue, please let me know. Thanks! |
It turns out that this has some pretty extensive repurcussions, and makes it impossible to use Bundler in some specific circumstances, like with gems that ship with Ruby, and with gems that are installed by distro packages. It also breaks the `bundle pack` command, because the gems that are cached by the pack command are not found by this check. See also: #2854 #2780 This reverts commit bd0243e.
It turns out that this has some pretty extensive repurcussions, and makes it impossible to use Bundler in some specific circumstances, like with gems that ship with Ruby, and with gems that are installed by distro packages. It also breaks the `bundle pack` command, because the gems that are cached by the pack command are not found by this check. See also: #2854 #2780 This reverts commit bd0243e.
Thanks a lot! |
It turns out that this has some pretty extensive repurcussions, and makes it impossible to use Bundler in some specific circumstances, like with gems that ship with Ruby, and with gems that are installed by distro packages. It also breaks the `bundle pack` command, because the gems that are cached by the pack command are not found by this check. See also: #2854 #2818 #2780 This reverts commit bd0243e.
bundle 1.5.3 does not seem to have resolved the problem. |
Did not fix for me either, but I did find a workaround, which was to manually run "gem install minitest -v 4.7.5" and "gem install json -v 1.8.1" commands. For some reason "bundle install" finds those gems while "bundle package" does not until after manual installation. |
uhh... hmm. 1.5.3 reverted the code that caused this problem in the first place, so that's very weird. On Tue, Feb 11, 2014 at 8:42 AM, Mathew Kamkar [email protected]
|
Is this being taken up in a new issue # or should it perhaps be open, as the symptom is present when packaging with 1.5.3? |
#2869 is attempting to address this issue. |
Having the same issue using 1.5.3, trying to run "bundle install" after creating a fresh rails app gives me the same minitest error. Using 1.5.0, no minitest error but I did get the json error. |
Then that's not the same error and you should probably check out ISSUES, after upgrading to Bundler 1.6 rc with 'gem install bundler --pre'. On Tue, Mar 18, 2014 at 12:43 AM, aquateen [email protected]
|
I'll try 1.6rc, but how is it not the same error? I get the same error messages and my env settings look the same as aluappinheiro (using 1.5.3 and then 1.5.1). |
Sorry, I misread your comment as saying you were only having issues with JSON. :/ If 1.6 isn't fixing your issue then it sounds like your ruby install is somehow missing the minitest gem that ships with Ruby. On Tue, Mar 18, 2014 at 10:16 AM, aquateen [email protected]
|
Looks like I'm running into the same issue:
I'm able to get things working if I use this instead:
|
Unfortunately that's not enough information for me to reproduce your problem. Please see ISSUES. On Sat, Mar 29, 2014 at 6:28 PM, Ryan Mohr [email protected]
|
The full Here's the script that was used to install everything:
And the output from
|
I'm also using 1.6.0 and am encountering this issue. If it's pertinent, we're using nginx + unicorn. |
My current guess is that your system-packaged ruby does not include the minitest gem, but your ruby installation in development does. Can you check that? On Apr 1, 2014, at 12:05 PM, Benjamin Deming [email protected] wrote:
|
@indirect Thanks for the quick response – the problem just ended up being some extremely obscure issue that resolved itself spontaneously when changing the unicorn binary we were using. Nothing related to bundler it seems. |
Probably your unicorn binary was running under a different Ruby (possibly an older version?) that did not include the minitest gem as a built-in. On Apr 1, 2014, at 1:01 PM, Benjamin Deming [email protected] wrote:
|
OK, yes, that was actually it, had to defer to another team member for confirmation. Unicorn was running under Ruby 1.9.3 instead of 2.1.0. |
Glad to hear that the issue is actually fixed with Bundler 1.6! Thanks for reporting back. On Apr 1, 2014, at 1:04 PM, Benjamin Deming [email protected] wrote:
|
I'm having the same issue. I'm brand new to Ruby and Rails, so I might need some coaching on how to provide the right info to determine if this is a problem or not. I'm using Rails 4.0.3, Bundler 1.6.0.rc, and rbenv 0.4.0. I have Ruby version 2.1.0 installed via rbenv. To be honest, I'm not sure I have any of that installed correctly. User error definitely could be the root of my issue. If I check here:
I see "minitest-5.3.1" listed (and minitest_rails-0.9.2, and a bunch of others). I'm not referencing minitest directly in my Gemfile.lock, but I am referencing: minitest-rails My Gemfile.lock shows "minitest(4.7.5)" I don't know why. Shouldn't it reference the one in my 2.1.0 installation? And if so, shouldn't that solve the problem? It seems like my Gemfile.lock is getting stuck with an old version. When I run
I get "minitest (5.3.1, 4.7.5)", so it looks like they're both installed. But I'm not sure I understand where the Ruby that came with my system (looks like both 1.8.0 and 2.0.0 are on my brand new iMac) lives. If I search for stuff starting with "minitest-", I see these locations:
Maybe that first location is where the 4.7.5 is coming from? Regardless, I thought having my .ruby-version file in my Rails app say "2.1.0", and having version 2.1.0 installed via rbenv, would make my Gemfile.lock use the gems for version 2.1.0. Apparently not, so I'm a little confused about how to get rid of the 4.7.5 issue. And all of that versioning stuff aside, apparently my vendor/cache directory doesn't get any version of the minitest gem in it after I run "bundle package". So even if I understood the versioning issue, I would still end up without the gem in cache, and my deploys would fail. Very frustrating. I'll take any help you folks are willing to give. Roy |
I'm not super clear on exactly where your problem is beyond there being an error related to the minitest gem. Can you follow https://github.com/carlhuda/bundler/blob/master/ISSUES.md and open a new ticket? On Mon, Apr 7, 2014 at 8:40 AM, dvlscm [email protected] wrote:
|
This error persists in my app.
gem 'rails', '4.0.2'
This problem stopped my deployment process in production. Locally I have the same problem but my app works. Any idea to fix this problem??
The text was updated successfully, but these errors were encountered: