bughit

as a consequence, deleting the gem from the cache effectively uninstalls it, breaking dependents This has got to be a bug, no way should the removal of a gem from...

## Environment ``` Bundler 1.14.3 Rubygems 2.6.8 Ruby 2.4.0p0 (2016-12-24 revision 57164) [x86_64-linux] Git 2.11.0 Platform x86_64-linux ``` ## Bundler settings ``` cache_all Set for your local app (/tmp/bundler_cache_bug/.bundle/config): "true"...

> This could be working as intended? The install cache is meant to hold gems downloaded from their source in order to avoid downloading them again (for perf or security...

This has the following additional consequence If a gem has a native extension, the extension will get installed into the global git gem location (this may be new in 1.15.x,...

I pointed out that the severity is higher than it first seemed. Using `gem 'puma', github: 'puma'`, running bundle install and then not being able to run puma, is more...

doesn't look like you're vendor caching gems in your project [bundler_cache_bug.zip](https://github.com/bundler/bundler/files/1126609/bundler_cache_bug.zip) in the attached project, bundle install, run puma

as to the fix, I discovered that if you run bundle install a second time it will add the binary extension to the cache and puma will start loading (from...

The zip attached in https://github.com/bundler/bundler/issues/5398#issuecomment-313280867 https://github.com/bundler/bundler/files/1126609/bundler_cache_bug.zip does have .bundle folder with a config file with `BUNDLE_CACHE_ALL: "true"` I just double checked. You do not need to run `bundle pack --all`...

@deivid-rodriguez > instead of making sure git gems are not looked up in the cache location but in the real install location That's the second part, the first is to...

> I think the gem is actually installed to the proper location When I reported this they definitely weren't. I'll try the current version at some point.