Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Bundle package broken after 1.7.14 #1973
There is a bunch of new bundled gems in 1.7.14:
This happens because bundler makes assumption that bundled gems's gemspecs are inside
def builtin_gem?(spec) # Ruby 2.1, where all included gems have this summary return true if spec.summary =~ /is bundled with Ruby/ # Ruby 2.0, where gemspecs are stored in specifications/default/ spec.loaded_from && spec.loaded_from.include?("specifications/default/") end
the gems are installed in jruby-1.7.15/lib/ruby/gems/shared/gems
I tried to reproduce the issue with fresh jruby-1.7.15 install from a
are you using rbenv or rvm or chruby or ... ?
Absence of cached gems is exactly the reason of issue.
Here are gem and steps to reproduce: https://gist.github.com/etehtsea/1d0cadda39e683517d1c
gem uninstall -aIx `gem list --no-versions |grep -vE 'rdoc|krypt|rake|jruby-openssl|jar-dependencies|ffi|json'`
P.S. But I don't understand - if this gems have no deps why they become pre-installed?
thanx for the gist - still works for me.
from your gist I see one thing which looks odd:
you execute all the code inside
but bundler reports a warning like this
issue-repro at /private/tmp/issue-repro did not have a valid gemspec.
which is a different directory ! can this be the cause you are seeing a
I was just looking for something which might be different. yes, I made a
my remote box of yours, does work once the gem file is in the cache folder.
thanx for your help ;)