Skip to content
This repository has been archived by the owner on Apr 14, 2021. It is now read-only.

Could not find minitest-4.7.5.gem for installation #2854

Closed
aluappinheiro opened this issue Feb 3, 2014 · 25 comments
Closed

Could not find minitest-4.7.5.gem for installation #2854

aluappinheiro opened this issue Feb 3, 2014 · 25 comments

Comments

@aluappinheiro
Copy link

This error persists in my app.

bundle package
Using rake (10.1.1)
Using i18n (0.6.9)
Using minitest (4.7.5)
Using multi_json (1.8.4)
...
..
Could not find minitest-4.7.5.gem for installation

bundle env
Bundler 1.5.2
Ruby 2.1.0 (2013-12-25 patchlevel 0) [i686-linux]
Rubygems 2.2.1
rvm 1.25.12 (stable)
GEM_HOME /home/aluap.pinheiro/.rvm/gems/ruby-2.1.0-p0
GEM_PATH /home/aluap.pinheiro/.rvm/gems/ruby-2.1.0-p0:/home/susanbrumbaugh/.rvm/gems/ruby-2.1.0-p0@global
rubygems-bundler (1.4.2)

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??

@indirect
Copy link
Member

indirect commented Feb 3, 2014

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!

@aluappinheiro
Copy link
Author

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
Ruby 2.1.0 (2013-12-25 patchlevel 0) [i686-linux]
Rubygems 2.2.0
rvm 1.25.16 (stable)
GEM_HOME /home/susanbrumbaugh/.rvm/gems/ruby-2.1.0@boColetivo
GEM_PATH /home/susanbrumbaugh/.rvm/gems/ruby-2.1.0@boColetivo:/home/susanbrumbaugh/.rvm/gems/ruby-2.1.0@global
rubygems-bundler (1.4.2)

Bundler settings
path
Set for your local app (/home/susanbrumbaugh/Workspace/boColetivo/.bundle/config): "vendor/bundle"
disable_shared_gems
Set for your local app (/home/susanbrumbaugh/Workspace/boColetivo/.bundle/config): "1"

Gemfile
source 'https://rubygems.org'

gem 'rails', '4.0.2'
gem 'omniauth'
gem 'omniauth-facebook'

gem 'mysql2'

gem 'sass-rails', '> 4.0.0'
gem 'uglifier', '>= 1.3.0'
Use CoffeeScript for .js.coffee assets and views
gem 'coffee-rails', '
> 4.0.0'

gem 'jquery-rails'
gem 'gmaps4rails'

gem 'turbolinks'
gem 'jbuilder', '~> 1.2'

Gemfile.lock
GEM
remote: https://rubygems.org/
specs:
actionmailer (4.0.2)
actionpack (= 4.0.2)
mail (> 2.5.4)
actionpack (4.0.2)
activesupport (= 4.0.2)
builder (
> 3.1.0)
erubis (> 2.7.0)
rack (
> 1.5.2)
rack-test (> 0.6.2)
activemodel (4.0.2)
activesupport (= 4.0.2)
builder (
> 3.1.0)
activerecord (4.0.2)
activemodel (= 4.0.2)
activerecord-deprecated_finders (> 1.0.2)
activesupport (= 4.0.2)
arel (
> 4.0.0)
activerecord-deprecated_finders (1.0.3)
activesupport (4.0.2)
i18n (> 0.6, >= 0.6.4)
minitest (
> 4.2)
multi_json (> 1.3)
thread_safe (
> 0.1)
tzinfo (> 0.3.37)
arel (4.0.1)
atomic (1.1.14)
builder (3.1.4)
coffee-rails (4.0.1)
coffee-script (>= 2.2.0)
railties (>= 4.0.0, < 5.0)
coffee-script (2.2.0)
coffee-script-source
execjs
coffee-script-source (1.7.0)
erubis (2.7.0)
execjs (2.0.2)
faraday (0.9.0)
multipart-post (>= 1.2, < 3)
gmaps4rails (2.1.1)
hashie (2.0.5)
hike (1.2.3)
i18n (0.6.9)
jbuilder (1.5.3)
activesupport (>= 3.0.0)
multi_json (>= 1.2.0)
jquery-rails (3.1.0)
railties (>= 3.0, < 5.0)
thor (>= 0.14, < 2.0)
json (1.8.1)
jwt (0.1.11)
multi_json (>= 1.5)
mail (2.5.4)
mime-types (
> 1.16)
treetop (> 1.4.8)
mime-types (1.25.1)
minitest (4.7.5)
multi_json (1.8.4)
multi_xml (0.5.5)
multipart-post (2.0.0)
mysql2 (0.3.15)
oauth2 (0.9.3)
faraday (>= 0.8, < 0.10)
jwt (
> 0.1.8)
multi_json (> 1.3)
multi_xml (
> 0.5)
rack (> 1.2)
omniauth (1.2.1)
hashie (>= 1.2, < 3)
rack (
> 1.0)
omniauth-facebook (1.6.0)
omniauth-oauth2 (> 1.1)
omniauth-oauth2 (1.1.2)
faraday (>= 0.8, < 0.10)
multi_json (
> 1.3)
oauth2 (> 0.9.3)
omniauth (
> 1.2)
polyglot (0.3.3)
rack (1.5.2)
rack-test (0.6.2)
rack (>= 1.0)
rails (4.0.2)
actionmailer (= 4.0.2)
actionpack (= 4.0.2)
activerecord (= 4.0.2)
activesupport (= 4.0.2)
bundler (>= 1.3.0, < 2.0)
railties (= 4.0.2)
sprockets-rails (> 2.0.0)
railties (4.0.2)
actionpack (= 4.0.2)
activesupport (= 4.0.2)
rake (>= 0.8.7)
thor (>= 0.18.1, < 2.0)
rake (10.1.1)
rdoc (4.1.1)
json (
> 1.4)
sass (3.2.14)
sass-rails (4.0.1)
railties (>= 4.0.0, < 5.0)
sass (>= 3.1.10)
sprockets-rails (> 2.0.0)
sdoc (0.4.0)
json (
> 1.8)
rdoc (> 4.0, < 5.0)
sprockets (2.10.1)
hike (
> 1.2)
multi_json (> 1.0)
rack (
> 1.0)
tilt (> 1.1, != 1.3.0)
sprockets-rails (2.0.1)
actionpack (>= 3.0)
activesupport (>= 3.0)
sprockets (
> 2.8)
thor (0.18.1)
thread_safe (0.1.3)
atomic
tilt (1.4.1)
treetop (1.4.15)
polyglot
polyglot (>= 0.3.1)
turbolinks (2.2.1)
coffee-rails
tzinfo (0.3.38)
uglifier (2.4.0)
execjs (>= 0.3.0)
json (>= 1.8.0)

PLATFORMS
ruby

DEPENDENCIES
coffee-rails (> 4.0.0)
gmaps4rails
jbuilder (
> 1.2)
jquery-rails
mysql2
omniauth
omniauth-facebook
rails (= 4.0.2)
sass-rails (~> 4.0.0)
sdoc
turbolinks
uglifier (>= 1.3.0)

@HollowerMan
Copy link

I am also having this exact same issue.

@indirect
Copy link
Member

indirect commented Feb 6, 2014

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!

@indirect indirect closed this as completed Feb 6, 2014
indirect added a commit that referenced this issue Feb 6, 2014
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.
indirect added a commit that referenced this issue Feb 6, 2014
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.
@HollowerMan
Copy link

Thanks a lot!
I'm looking forward for this 1.5.3. I'll let you know if it fixes my issue.

indirect added a commit that referenced this issue Feb 6, 2014
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.
@pungoyal
Copy link

bundle 1.5.3 does not seem to have resolved the problem.

@matkam
Copy link

matkam commented Feb 11, 2014

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.

@indirect
Copy link
Member

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]
wrote:

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.

Reply to this email directly or view it on GitHub:
#2854 (comment)

@ylg
Copy link

ylg commented Feb 16, 2014

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?

@indirect
Copy link
Member

#2869 is attempting to address this issue.

@aquateen
Copy link

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.

@indirect
Copy link
Member

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]
wrote:

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.

Reply to this email directly or view it on GitHub:
#2854 (comment)

@aquateen
Copy link

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).

@indirect
Copy link
Member

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]
wrote:

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).

Reply to this email directly or view it on GitHub:
#2854 (comment)

@rymohr
Copy link

rymohr commented Mar 29, 2014

Looks like I'm running into the same issue:

$ bundle -v
Bundler version 1.6.0

$ gem list | grep rake
rake (10.1.1)

$ bundle list | grep rake
  * rake (10.1.1)

$ bundle package --all
Could not find rake-10.1.1.gem for installation

I'm able to get things working if I use this instead:

bundle install --path vendor/bundle
bundle package --all

@indirect
Copy link
Member

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]
wrote:

Looks like I'm running into the same issue:

$ bundle -v
Bundler version 1.6.0
$ gem list | grep rake
rake (10.1.1)
$ bundle list | grep rake
  * rake (10.1.1)
$ bundle package --all
Could not find rake-10.1.1.gem for installation

I'm able to get things working if I use this instead:

bundle install --path vendor/bundle
bundle package --all

Reply to this email directly or view it on GitHub:
#2854 (comment)

@rymohr
Copy link

rymohr commented Mar 30, 2014

The full bundle env output for this machine (ubuntu 12.04) is included below. The only thing that jumps out at me is that GEM_HOME is unset.

Here's the script that was used to install everything:

# ubuntu 12.04
apt-add-repository -y ppa:brightbox/ruby-ng
apt-get update -y

# Install ruby 2.0
apt-get install -y ruby2.0 ruby2.0-dev rubygems ruby-switch

# Set ruby 2.0 as the default
ruby-switch --set ruby2.0

# Install bundler
gem install bundler -v 1.6.0

And the output from bundle env:

Bundler 1.6.0
Ruby 2.0.0 (2013-11-22 patchlevel 353) [x86_64-linux-gnu]
Rubygems 2.0.14
GEM_HOME 

Bundler settings
  path
    Set for your local app (/tmp/src/.bundle/config): "vendor/bundle"
  disable_shared_gems
    Set for your local app (/tmp/src/.bundle/config): "1"
  cache_all
    Set for your local app (/tmp/src/.bundle/config): "true"


Gemfile
source 'https://rubygems.org'
ruby '2.0.0'

gem 'rails', '4.0.3'
gem 'couchrest', '~> 1.2.0'
gem 'inherited_resources', '~> 1.4.0'
gem 'responders', '~> 1.0.0'
gem 'rack-cors', '~> 0.2.7', :require => 'rack/cors'
gem 'cancan', '~> 1.6.10'
gem 'gaffe', '~> 1.0.1'
gem 'excon', '~> 0.27.6'
gem 'organized_routes', '~> 1.0.0'
gem 'friendly_id', '~> 5.0.2'
gem 'babosa', '~> 0.3.11'
gem 'unicode', '~> 0.4.4'
gem 'bcrypt-ruby', '~> 3.1.2'
gem 'enumerize', '~> 0.7.0'
gem 'github-markdown', '~> 0.5.5'
gem 'simple_form', '~> 3.0.1'
gem 'gravatar_image_tag', '~> 1.2.0'
gem 'flutie', '~> 2.0.0'
gem 'font-awesome-rails', '~> 3.2.1'
gem 'jquery-rails'
gem 'bourbon', '~> 3.1.8'
gem 'select2-rails', '~> 3.5.1'
gem 'dotenv-rails'
gem "therubyracer", "~> 0.12.1"
gem 'eco'
gem 'sprockets', '2.10.1'
gem 'sass-rails',   '~> 4.0.0'
gem 'coffee-rails', '~> 4.0.0'
gem 'uglifier', '>= 1.3.0'
gem 'bootstrap-sass', '~> 3.0.3.0'

group :development do
  gem 'quiet_assets'
  gem 'powder'
  gem 'brakeman', :require => false
end

group :development, :test do
  gem 'sqlite3'
  gem 'rspec-rails', '~> 2.14.0'
  gem 'jasmine-rails', '~> 0.5.6'
  gem 'fuubar', '~> 1.2.1'
  gem 'capybara', '~> 2.1.0'
  gem 'capybara-json'
  gem 'poltergeist', '~> 1.3.0'
  gem 'launchy'
  gem 'factory_girl_rails', '~> 4.4.0'
  gem 'database_cleaner'
  gem 'guard', '~> 1.8.2'
  gem 'guard-rspec', '~> 3.0.2'
  gem 'rb-fsevent', '~> 0.9.3'
end

group :production do
  gem 'pg', '0.17.1'
end



Gemfile.lock
GEM
  remote: https://rubygems.org/
  specs:
    actionmailer (4.0.3)
      actionpack (= 4.0.3)
      mail (~> 2.5.4)
    actionpack (4.0.3)
      activesupport (= 4.0.3)
      builder (~> 3.1.0)
      erubis (~> 2.7.0)
      rack (~> 1.5.2)
      rack-test (~> 0.6.2)
    activemodel (4.0.3)
      activesupport (= 4.0.3)
      builder (~> 3.1.0)
    activerecord (4.0.3)
      activemodel (= 4.0.3)
      activerecord-deprecated_finders (~> 1.0.2)
      activesupport (= 4.0.3)
      arel (~> 4.0.0)
    activerecord-deprecated_finders (1.0.3)
    activesupport (4.0.3)
      i18n (~> 0.6, >= 0.6.4)
      minitest (~> 4.2)
      multi_json (~> 1.3)
      thread_safe (~> 0.1)
      tzinfo (~> 0.3.37)
    addressable (2.3.5)
    arel (4.0.2)
    atomic (1.1.15)
    babosa (0.3.11)
    bcrypt-ruby (3.1.2)
    bootstrap-sass (3.0.3.0)
      sass (~> 3.2)
    bourbon (3.1.8)
      sass (>= 3.2.0)
      thor
    brakeman (2.4.1)
      erubis (~> 2.6)
      fastercsv (~> 1.5)
      haml (>= 3.0, < 5.0)
      highline (~> 1.6.20)
      multi_json (~> 1.2)
      ruby2ruby (~> 2.0.5)
      ruby_parser (~> 3.4.0)
      sass (~> 3.0)
      slim (>= 1.3.6, < 3.0)
      terminal-table (~> 1.4)
    builder (3.1.4)
    cancan (1.6.10)
    capybara (2.1.0)
      mime-types (>= 1.16)
      nokogiri (>= 1.3.3)
      rack (>= 1.0.0)
      rack-test (>= 0.5.4)
      xpath (~> 2.0)
    capybara-json (0.3.0)
      capybara
      httpclient (~> 2.2)
      multi_json (~> 1.3)
    coderay (1.1.0)
    coffee-rails (4.0.1)
      coffee-script (>= 2.2.0)
      railties (>= 4.0.0, < 5.0)
    coffee-script (2.2.0)
      coffee-script-source
      execjs
    coffee-script-source (1.6.3)
    couchrest (1.2.0)
      mime-types (~> 1.15)
      multi_json (~> 1.0)
      rest-client (~> 1.6.1)
    database_cleaner (1.2.0)
    diff-lcs (1.2.5)
    dotenv (0.9.0)
    dotenv-rails (0.9.0)
      dotenv (= 0.9.0)
    eco (1.0.0)
      coffee-script
      eco-source
      execjs
    eco-source (1.1.0.rc.1)
    enumerize (0.7.0)
      activesupport (>= 3.2)
    erubis (2.7.0)
    eventmachine (1.0.3)
    excon (0.27.6)
    execjs (2.0.2)
    factory_girl (4.4.0)
      activesupport (>= 3.0.0)
    factory_girl_rails (4.4.0)
      factory_girl (~> 4.4.0)
      railties (>= 3.0.0)
    fastercsv (1.5.5)
    faye-websocket (0.4.7)
      eventmachine (>= 0.12.0)
    ffi (1.9.3)
    flutie (2.0.0)
    font-awesome-rails (3.2.1.3)
      railties (>= 3.2, < 5.0)
    formatador (0.2.4)
    friendly_id (5.0.2)
      activerecord (~> 4.0.0)
    fuubar (1.2.1)
      rspec (~> 2.0)
      rspec-instafail (~> 0.2.0)
      ruby-progressbar (~> 1.0)
    gaffe (1.0.1)
      rails (>= 3.2.0)
    github-markdown (0.5.5)
    gravatar_image_tag (1.2.0)
    guard (1.8.3)
      formatador (>= 0.2.4)
      listen (~> 1.3)
      lumberjack (>= 1.0.2)
      pry (>= 0.9.10)
      thor (>= 0.14.6)
    guard-rspec (3.0.3)
      guard (>= 1.8)
      rspec (~> 2.13)
    haml (4.0.5)
      tilt
    has_scope (0.6.0.rc)
      actionpack (>= 3.2, < 5)
      activesupport (>= 3.2, < 5)
    highline (1.6.21)
    hike (1.2.3)
    http_parser.rb (0.5.3)
    httpclient (2.3.4.1)
    i18n (0.6.9)
    inherited_resources (1.4.1)
      has_scope (~> 0.6.0.rc)
      responders (~> 1.0.0.rc)
    jasmine-core (1.3.1)
    jasmine-rails (0.5.6)
      jasmine-core (~> 1.3)
      phantomjs
      rails (>= 3.1.0)
      sprockets-rails
    jquery-rails (3.0.4)
      railties (>= 3.0, < 5.0)
      thor (>= 0.14, < 2.0)
    json (1.8.1)
    launchy (2.4.2)
      addressable (~> 2.3)
    libv8 (3.16.14.3)
    listen (1.3.1)
      rb-fsevent (>= 0.9.3)
      rb-inotify (>= 0.9)
      rb-kqueue (>= 0.2)
    lumberjack (1.0.4)
    mail (2.5.4)
      mime-types (~> 1.16)
      treetop (~> 1.4.8)
    method_source (0.8.2)
    mime-types (1.25.1)
    mini_portile (0.5.2)
    minitest (4.7.5)
    multi_json (1.9.0)
    nokogiri (1.6.1)
      mini_portile (~> 0.5.0)
    organized_routes (1.0.0)
    pg (0.17.1)
    phantomjs (1.9.2.1)
    poltergeist (1.3.0)
      capybara (~> 2.1.0)
      faye-websocket (>= 0.4.4, < 0.5.0)
      http_parser.rb (~> 0.5.3)
    polyglot (0.3.4)
    powder (0.2.0)
      thor (>= 0.11.5)
    pry (0.9.12.4)
      coderay (~> 1.0)
      method_source (~> 0.8)
      slop (~> 3.4)
    quiet_assets (1.0.2)
      railties (>= 3.1, < 5.0)
    rack (1.5.2)
    rack-cors (0.2.9)
    rack-test (0.6.2)
      rack (>= 1.0)
    rails (4.0.3)
      actionmailer (= 4.0.3)
      actionpack (= 4.0.3)
      activerecord (= 4.0.3)
      activesupport (= 4.0.3)
      bundler (>= 1.3.0, < 2.0)
      railties (= 4.0.3)
      sprockets-rails (~> 2.0.0)
    railties (4.0.3)
      actionpack (= 4.0.3)
      activesupport (= 4.0.3)
      rake (>= 0.8.7)
      thor (>= 0.18.1, < 2.0)
    rake (10.1.1)
    rb-fsevent (0.9.3)
    rb-inotify (0.9.3)
      ffi (>= 0.5.0)
    rb-kqueue (0.2.0)
      ffi (>= 0.5.0)
    ref (1.0.5)
    responders (1.0.0)
      railties (>= 3.2, < 5)
    rest-client (1.6.7)
      mime-types (>= 1.16)
    rspec (2.14.1)
      rspec-core (~> 2.14.0)
      rspec-expectations (~> 2.14.0)
      rspec-mocks (~> 2.14.0)
    rspec-core (2.14.7)
    rspec-expectations (2.14.4)
      diff-lcs (>= 1.1.3, < 2.0)
    rspec-instafail (0.2.4)
    rspec-mocks (2.14.4)
    rspec-rails (2.14.0)
      actionpack (>= 3.0)
      activesupport (>= 3.0)
      railties (>= 3.0)
      rspec-core (~> 2.14.0)
      rspec-expectations (~> 2.14.0)
      rspec-mocks (~> 2.14.0)
    ruby-progressbar (1.3.2)
    ruby2ruby (2.0.7)
      ruby_parser (~> 3.1)
      sexp_processor (~> 4.0)
    ruby_parser (3.4.1)
      sexp_processor (~> 4.1)
    sass (3.2.13)
    sass-rails (4.0.1)
      railties (>= 4.0.0, < 5.0)
      sass (>= 3.1.10)
      sprockets-rails (~> 2.0.0)
    select2-rails (3.5.2)
      thor (~> 0.14)
    sexp_processor (4.4.1)
    simple_form (3.0.1)
      actionpack (>= 4.0.0, < 4.1)
      activemodel (>= 4.0.0, < 4.1)
    slim (2.0.2)
      temple (~> 0.6.6)
      tilt (>= 1.3.3, < 2.1)
    slop (3.4.7)
    sprockets (2.10.1)
      hike (~> 1.2)
      multi_json (~> 1.0)
      rack (~> 1.0)
      tilt (~> 1.1, != 1.3.0)
    sprockets-rails (2.0.1)
      actionpack (>= 3.0)
      activesupport (>= 3.0)
      sprockets (~> 2.8)
    sqlite3 (1.3.8)
    temple (0.6.7)
    terminal-table (1.4.5)
    therubyracer (0.12.1)
      libv8 (~> 3.16.14.0)
      ref
    thor (0.18.1)
    thread_safe (0.2.0)
      atomic (>= 1.1.7, < 2)
    tilt (1.4.1)
    treetop (1.4.15)
      polyglot
      polyglot (>= 0.3.1)
    tzinfo (0.3.39)
    uglifier (2.4.0)
      execjs (>= 0.3.0)
      json (>= 1.8.0)
    unicode (0.4.4)
    xpath (2.0.0)
      nokogiri (~> 1.3)

PLATFORMS
  ruby

DEPENDENCIES
  babosa (~> 0.3.11)
  bcrypt-ruby (~> 3.1.2)
  bootstrap-sass (~> 3.0.3.0)
  bourbon (~> 3.1.8)
  brakeman
  cancan (~> 1.6.10)
  capybara (~> 2.1.0)
  capybara-json
  coffee-rails (~> 4.0.0)
  couchrest (~> 1.2.0)
  database_cleaner
  dotenv-rails
  eco
  enumerize (~> 0.7.0)
  excon (~> 0.27.6)
  factory_girl_rails (~> 4.4.0)
  flutie (~> 2.0.0)
  font-awesome-rails (~> 3.2.1)
  friendly_id (~> 5.0.2)
  fuubar (~> 1.2.1)
  gaffe (~> 1.0.1)
  github-markdown (~> 0.5.5)
  gravatar_image_tag (~> 1.2.0)
  guard (~> 1.8.2)
  guard-rspec (~> 3.0.2)
  inherited_resources (~> 1.4.0)
  jasmine-rails (~> 0.5.6)
  jquery-rails
  launchy
  organized_routes (~> 1.0.0)
  pg (= 0.17.1)
  poltergeist (~> 1.3.0)
  powder
  quiet_assets
  rack-cors (~> 0.2.7)
  rails (= 4.0.3)
  rb-fsevent (~> 0.9.3)
  responders (~> 1.0.0)
  rspec-rails (~> 2.14.0)
  sass-rails (~> 4.0.0)
  select2-rails (~> 3.5.1)
  simple_form (~> 3.0.1)
  sprockets (= 2.10.1)
  sqlite3
  therubyracer (~> 0.12.1)
  uglifier (>= 1.3.0)
  unicode (~> 0.4.4)

@bendeming
Copy link

I'm also using 1.6.0 and am encountering this issue. If it's pertinent, we're using nginx + unicorn.

@indirect
Copy link
Member

indirect commented Apr 1, 2014

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:

I'm also using 1.6.0 and am encountering this issue. If it helps, we're using nginx + unicorn.


Reply to this email directly or view it on GitHub.

@bendeming
Copy link

@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.

@indirect
Copy link
Member

indirect commented Apr 1, 2014

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:

@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.


Reply to this email directly or view it on GitHub.

@bendeming
Copy link

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.

@indirect
Copy link
Member

indirect commented Apr 1, 2014

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:

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.


Reply to this email directly or view it on GitHub.

@dvlscm
Copy link

dvlscm commented Apr 7, 2014

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:

~/.rbenv/versions/2.1.0/lib/ruby/gems/2.1.0/gems

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
minitest-rails-capybara
minitest-colorize
minitest-focus

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

gem list minitest

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:

/Users/[me]/.gem/specs/rubygems.org%443/quick/Marshal.4.8/minitest-4.7.5.gemspec
[other files...]
/Users/[me]/.rbenv/versions/2.1.0/lib/ruby/gems/2.1.0/gems/minitest-5.3.1

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

@indirect
Copy link
Member

indirect commented Apr 7, 2014

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:

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:

~/.rbenv/versions/2.1.0/lib/ruby/gems/2.1.0/gems

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
minitest-rails-capybara
minitest-colorize
minitest-focus
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

gem list minitest

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:

/Users/[me]/.gem/specs/rubygems.org%443/quick/Marshal.4.8/minitest-4.7.5.gemspec
[other files...]
/Users/[me]/.rbenv/versions/2.1.0/lib/ruby/gems/2.1.0/gems/minitest-5.3.1

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. I'll take any help you folks are willing to give.

Roy

Reply to this email directly or view it on GitHub:
#2854 (comment)

pjaspers pushed a commit to pjaspers/foodz that referenced this issue Jul 31, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants