`bundle install` fails (because of git protocol)
Don't use the github:
short form in your Gemfile, just use the regular git:
syntax
gem 'activerecord-sqlserver-adapter', git: 'http://github.com/arthrex/activerecord-sqlserver-adapter.git'
Force bundle install to use https:// instead of git:// for GitHub-based gems
Git provides URL rewriting functionality using the url..insteadOf configuration option.
So to make all connections to github.com use https:// rather than git://
git config --global url."https://github.com".insteadOf git://github.com
The --global
switch sets the config option for all git operations by the current user, so there are times where it may be too intrusive. But it does avoid changing the git config in the current project.
Running bundle install changes git:// to https:// in Gemfile.lock
Upgrading to Bundler 1.7.2 seems to solve the problem.
Bundler having trouble with Git
This is because the file you are trying to run has a syntax that belongs to Ruby 1.9 and you have an older version installed on your computer. You need to update it.
I don't know which OS are you using. Install Ruby 1.9 on CentOS is a guide for CentOS and it might give you an idea on how to update it.
Or use RVM. It will make your life easier.
The unauthenticated git protocol on port 9418 is no longer supported
@toast-ui/react-chart dependency is causing issue for you here.
If you look closely inside your package-lock.json you can backtrack eve to @toast-ui/react-chart
eve --> raphael --> tui-chart --> @toast-ui/react-chart
You can follow this same technique to find any more issues inside your project.
Error when bundling one year old Rails app on new machine w latest Ruby (2.4.1) + Rails
If you need to remove a gem you should remove it from your Gemfile
, not Gemfile.lock
.
In your Gemfile
: gem 'json', github: 'flori/json', branch: 'v1.8'
bundler
creates Gemfile.lock
for you after it resolves your dependencies during bundle install
, based on whatever's in your Gemfile
. Gemfile.lock
also specifies gems that are not in your Gemfile
but are dependencies of gems that are. Editing it manually is almost guaranteed to cause you problems and fix nothing.
But you probably don't need to remove it at all. Right now you're locked onto a version of json
that bundler
's having trouble resolving. You should delete Gemfile.lock
and let bundler
generate a brand new one.
error: fatal: I don't handle protocol ``git` when using bundle install
It's the issue with the newer version of the Bundler 1.0.14.
I needed to revert to 1.0.13 to make it work. They apparently had some issues dealing with escape characters in Windows.
See here > https://github.com/carlhuda/bundler/issues/1212
Related Topics
How to Make a Ruby Script Using Trollop for Command Line Parsing
Error Creating Rails Db Using Rake Db:Create
Ruby 'Gets' That Works Over Multiple Lines
How to Use Headless Chrome with Capybara and Selenium
Rails 4 Error with Every Command "'Load': No Implicit Conversion of Nil into String" (MAC Os X 10.9)
How Does Count Method Works in Ruby
Cron Is Running in Home Directory Instead of File Directory
Shortening Socket Timeout Using Timeout::Timeout(N) Does Not Seem to Work for Me
Advice on How to Validate Names and Surnames Using Regex
Nanoc Changing the Base Path When Deploying Page in Github
Ruby/Rails Array of Strings to Postgresql Insert
The Program 'Rails' Is Currently Not Installed
Flash Message with HTML_Safe from the Controller in Rails 4 (Safe Version)
Is There an Elegant Way to Exclude the First Value of a Range
Trouble with Google Apps API and Service Accounts in Ruby
Catching Command-Line Errors Using %X
Error:'Incompatible Library Version' SQLite3-1.3.11 in Rails
Ruby Looks for Class Variable in the Object Instead of Specific Class