Skip to content
This repository has been archived by the owner on May 12, 2018. It is now read-only.

Update Gemfile.lock for version 5.2.0 #24

Closed

Conversation

edvakf
Copy link
Contributor

@edvakf edvakf commented Feb 9, 2014

I get the following error with commit a26ba07 (Version 5.2.0)

% bundle install --path=vendor/bundle --deployment
Fetching gem metadata from http://rubygems.org/.........
Fetching additional metadata from http://rubygems.org/..
Could not find gitlab_git-5.1.0 in any of the sources

This could be fixed by updating Gemfile.lock (or bundle install --no-deployment).

just for your information:

% ruby --version
ruby 2.1.0p0 (2013-12-25 revision 44422) [x86_64-darwin13.0]
% bundle --version
Bundler version 1.5.3

This fixes `bundle install --deployment` failure with
"Could not find gitlab_git-5.1.0 in any of the sources"
@edvakf
Copy link
Contributor Author

edvakf commented Feb 9, 2014

OK, now the error in blob_spec.rb on Ruby 1.9.3 comes from the fact that the default internal encoding was US_ASCII before 2.0. I'm going to put another commit for it.

@coveralls
Copy link

Coverage Status

Changes Unknown when pulling f88a40d on edvakf:fix/gemfile_lock_for_version_5_2 into * on gitlabhq:master*.

Ruby 1.9.x's default internal encoding was US_ASCII,
so this file causes syntax error without the magic comment.
@coveralls
Copy link

Coverage Status

Changes Unknown when pulling fa42282 on edvakf:fix/gemfile_lock_for_version_5_2 into * on gitlabhq:master*.

@dzaporozhets
Copy link
Member

Thanks. BUt its not needed any more. I noticed your PR too late

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
3 participants