persisting `gem pristine --all` warning with bundled gems

[senny]

Even after calling gem pristine --all I get the same warning. According to the unstubbed collection the affected gems are:

["Ascii85", "actionmailer", "actionmailer", "actionpack",
"actionpack", "activemodel", "activemodel", "activerecord",
"activerecord", "activerecord-deprecated_finders", "activesupport",
"activesupport", "afm", "arel", "atomic", "axlsx", "backports",
"bcrypt-ruby", "bootstrap-datepicker-rails", "bootstrap-sass",
"builder", "capybara", "carrierwave", "cliver", "coffee-rails",
"coffee-rails", "coffee-script", "coffee-script-source",
"descendants_tracker", "devise", "dumpster", "erubis", "execjs",
"execjs", "factory_girl", "hashery", "hike", "htmlentities", "i18n",
"i18n", "jbuilder", "jquery-rails", "jquery-ui-rails", "json",
"kaminari", "libv8", "mail", "mime-types", "mime-types",
"mini_portile", "minitest", "multi_json", "nokogiri", "orm_adapter",
"paper_trail", "pdf-reader", "pg", "poltergeist", "polyglot", "prawn",
"rack", "rack-test", "rails", "rails", "railties", "railties", "rake",
"rdoc", "ref", "ruby-rc4", "rubyzip", "sass", "sass-rails", "sdoc",
"spring", "spring", "sprockets", "sprockets", "sprockets-rails",
"therubyracer", "thor", "thread_safe", "tilt", "treetop", "ttfunk",
"turbolinks", "turbolinks", "tzinfo", "uglifier", "virtus", "warden",
"websocket-driver", "xpath"]

Which is more or less all bundled gems. I figured maybe calling bundle exec gem pristine --all might do the trick. This also looked promising as it started to work away. Sadly it failed with:

Cached gem for bundler-1.3.5 not found, attempting to fetch...
Fetching: bundler-1.3.5.gem (100%)
ERROR:  While executing gem ... (Gem::InstallError)
    invalid gem: No such file or directory - /Users/senny/.rbenv/versions/2.0.0-p353/lib/ruby/gems/2.0.0/gems/bundler-1.3.5/lib/cache/bundler-1.3.5.gem

So basically there are two issues when using bundled gems:

• We need to document that you need to run bundle exec XYZ
• bundle exec pristine --all does not work because of the missing bundler gem. (Adding it to the Gemfile did not solve the issue for me).

[jonleighton]

I reckon this issue comes from the fact that you are using a bundle path. I think it would be fixed if you deleted and then re-installed your bundle.

[jonleighton]

Actually, does that make sense? Where do these gems live on your system?

[senny]

@jonleighton makes perfect sense. rm -rf .bundle && bundle resolved it. Thanks man!

[jonleighton]

Cool, I tweaked the message ^^

[wonderer007]

rm -rf .bundle && bundle resolved it THANKS EVERYONE