Its a workaround for a bug in Bundler which can cause sources from github to be loaded via HTTP and not HTTPS – which makes it vulnerable to man in the middle attacks. git_source adds a source which you can use so that the gem is downloaded from a git repository instead of a package … Read more
Answer was similar to the one Wrikken posted — here’s what I did to fix it for the sake of future readers. (This is for RHEL 5.5 — similar but different commands apply for Ubuntu/Debian/etc.) Doing sudo yum list installed will print out all installed packages on your machine (note: yum on RHEL requires you … Read more
The executables bundle & bundler have the same functionality and therefore can be used interchangeably. You can see in the bundler/exe directory that the bundler executable just loads the bundle executable. It seems to me that the bundle command is more commonly used than the bundler command. The commands bundle & bundle install also have … Read more
To find out where gems are being installed to, run echo $GEM_HOME in a terminal. When using RVM, gems are installed into your RVM install as it changes $GEM_HOME. Running echo $GEM_HOME now would show a path into your RVM install. When Bundler is added to the mix, gems will either be installed in $GEM_HOME, … Read more
Since we’re using ruby you could do something like this I guess: bundle list | ruby -e ‘ARGF.readlines[1..-1].each {|l| g = l.split(” “); puts “Removing #{g[1]}”; `gem uninstall –force #{g[1]} -v #{g[2].gsub(/\(|\)/, “”)}`; }’ NOTE: Only lightly tested.
gem install bundler is how to do it. You may want to use a tool such as rbenv to manage gems.
I have same issue: remote: ! Failed to install gems via Bundler. if you see the problem is this: remote: Your bundle only supports platforms [“x86_64-darwin-16”] but your local platform remote: is x86_64-linux. Add the current platform to the lockfile with `bundle loc remote: –add-platform x86_64-linux` and try again. its mean this : Your bundle … Read more
It appears it’s a problem reported on the Homebrew github repo (https://github.com/mxcl/homebrew/issues/16625) blaming rmagick itself not supporting newer versions of imagemagick. On that same issue (https://github.com/mxcl/homebrew/issues/16625#issuecomment-11519383), you can find this link: https://coderwall.com/p/wnomjg which actually worked for me. This is what he does: cd /usr/local/Cellar/imagemagick/6.8.0-10/lib ln -s libMagick++-Q16.7.dylib libMagick++.dylib ln -s libMagickCore-Q16.7.dylib libMagickCore.dylib ln -s libMagickWand-Q16.7.dylib … Read more
bundle update and bundle install can both install the gems you specified in Gemfile but missing in gems. But bundle update does one thing more to upgrade: If the gems specified in Gemfile don’t have version, it will upgrade to whatever latest. If the gems specified in Gemfile have version controlled with ~>, it will … Read more
You need to set a build config option like so: bundle config build.pg –with-pg-config=/path/to/pg_config More info can be found in the bundle config command documentation