Accept Merge fails [with RVM?]
Closed
Accept Merge fails [with RVM?]
Created by: Kagetsuki
Merges through the GitLab interface are failing. The following error can be found in log/githost.log:
January 13, 2014 04:16 -> ERROR -> Command failed [1]: /usr/bin/git --git-dir=/home/git/gitlab-satellites/redacted/redacted/.git push origin master
remote: /usr/local/rvm/gems/ruby-2.0.0-p353@global/gems/bundler-1.3.5/lib/bundler/spec_set.rb:92:in `block in materialize': Could not find rake-10.1.0 in any of the sources (Bundler::GemNotFound)
remote: from /usr/local/rvm/gems/ruby-2.0.0-p353@global/gems/bundler-1.3.5/lib/bundler/spec_set.rb:85:in `map!'
remote: from /usr/local/rvm/gems/ruby-2.0.0-p353@global/gems/bundler-1.3.5/lib/bundler/spec_set.rb:85:in `materialize'
remote: from /usr/local/rvm/gems/ruby-2.0.0-p353@global/gems/bundler-1.3.5/lib/bundler/definition.rb:114:in `specs'
remote: from /usr/local/rvm/gems/ruby-2.0.0-p353@global/gems/bundler-1.3.5/lib/bundler/definition.rb:159:in `specs_for'
remote: from /usr/local/rvm/gems/ruby-2.0.0-p353@global/gems/bundler-1.3.5/lib/bundler/definition.rb:148:in `requested_specs'
remote: from /usr/local/rvm/gems/ruby-2.0.0-p353@global/gems/bundler-1.3.5/lib/bundler/environment.rb:18:in `requested_specs'
remote: from /usr/local/rvm/gems/ruby-2.0.0-p353@global/gems/bundler-1.3.5/lib/bundler/runtime.rb:13:in `setup'
remote: from /usr/local/rvm/gems/ruby-2.0.0-p353@global/gems/bundler-1.3.5/lib/bundler.rb:120:in `setup'
remote: from /usr/local/rvm/gems/ruby-2.0.0-p353@global/gems/bundler-1.3.5/lib/bundler/setup.rb:17:in `<top (required)>'
remote: from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
remote: from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
remote: error: hook declined to update refs/heads/master
To /home/git/repositories/redacted/redacted.git
! [remote rejected] master -> master (hook declined)
error: failed to push some refs to '/home/git/repositories/redacted/redacted.git
rake v 10.1.0 is installed in both the rvm gemset mentioned above and or system ruby 1.9.1. This has been occurring since 6.1, and unlike other reports of the same issue I did not have system ruby 1.8 installed to begin with. Any ideas?
Please register or sign in to reply