Ah, yes. Having 2 rubies in the system causes conflicts. Some have reported errors in merge requests. If you don't use 1.9.1 you can safely remove it.
On Fri, Aug 15, 2014 at 5:33 PM, Ryan You <[email protected]> wrote: > thanks for the reply. this doesn't solve the problem but give me a good > hint of problem. > > for unknown reason my ruby 2.1.2 is install at /usr/local/bin/ruby instead > of /usr/bin/ruby > > /usr/bin/ruby is still 1.9.1 and bundle install/bundle exec doesn't work > when i tried to upgrade from 7.0 to 7.1 > I just make /usr/bin/ruby 2.1.2 then problem solved > > > On Friday, August 15, 2014 4:35:00 AM UTC-4, Achilleas Pipis wrote: > >> Try to `rm -r vendor/bundle` and do a bundle install again. >> >> >> On Thu, Aug 14, 2014 at 6:07 PM, Ryan You <[email protected]> wrote: >> >>> can anyone help? >>> >>> >>> On Tuesday, July 29, 2014 9:20:18 AM UTC-4, Ryan You wrote: >>>> >>>> Hi, >>>> >>>> I have a weird issue when upgrade gitlab from 7 to 7.1. The problem >>>> occurs at this step: >>>> >>>> sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production >>>> >>>> The error is >>>> >>>> Could not find minitest-5.3.5 in any of the sources >>>> Run `bundle install` to install missing gems >>>> >>>> I tried "bundle install" and get "using minitest-5.3.5" and "Your >>>> bundle is complete" >>>> >>>> The result of "sudo -u git gem list minitest" or "gem list minitest" is >>>> >>>> *** LOCAL GEMS *** >>>> >>>> minitest (5.4.0, 5.3.5, 4.7.5) >>>> >>>> Although gitlab is running without major problem with this install >>>> issue, it can't do auto merge now. The log show similar message: >>>> >>>> >>>> 1. >>>> >>>> July 29, 2014 08:53 -> ERROR -> Command failed [1]: /usr/bin/git >>>> --git-dir=/home/git/gitlab-satellites/risk/risk/.git >>>> --work-tree=/home/git/gitlab-satellites/risk/risk push origin dev >>>> 2. >>>> >>>> 3. >>>> >>>> remote: >>>> /usr/local/lib/ruby/gems/2.1.0/gems/bundler-1.6.5/lib/bundler/spec_set.rb:92:in >>>> `block in materialize': Could not find minitest-5.3.5 in any of the >>>> sources >>>> (Bundler::GemNotFound) >>>> 4. >>>> >>>> remote: from /usr/local/lib/ruby/gems/2.1.0/gems/bundler-1.6.5/lib/ >>>> bundler/spec_set.rb:85:in `map!' >>>> 5. >>>> >>>> remote: from /usr/local/lib/ruby/gems/2.1.0/gems/bundler-1.6.5/lib/ >>>> bundler/spec_set.rb:85:in `materialize' >>>> 6. >>>> >>>> remote: from /usr/local/lib/ruby/gems/2.1.0/gems/bundler-1.6.5/lib/ >>>> bundler/definition.rb:133:in `specs' >>>> 7. >>>> >>>> remote: from /usr/local/lib/ruby/gems/2.1.0/gems/bundler-1.6.5/lib/ >>>> bundler/definition.rb:178:in `specs_for' >>>> 8. >>>> >>>> remote: from /usr/local/lib/ruby/gems/2.1.0/gems/bundler-1.6.5/lib/ >>>> bundler/definition.rb:167:in `requested_specs' >>>> 9. >>>> >>>> remote: from /usr/local/lib/ruby/gems/2.1.0/gems/bundler-1.6.5/lib/ >>>> bundler/environment.rb:18:in `requested_specs' >>>> 10. >>>> >>>> remote: from /usr/local/lib/ruby/gems/2.1.0/gems/bundler-1.6.5/lib/ >>>> bundler/runtime.rb:13:in `setup' >>>> 11. >>>> >>>> remote: from /usr/local/lib/ruby/gems/2.1.0/gems/bundler-1.6.5/lib/ >>>> bundler.rb:120:in `setup' >>>> 12. >>>> >>>> remote: from /usr/local/lib/ruby/gems/2.1.0/gems/bundler-1.6.5/lib/ >>>> bundler/setup.rb:17:in `<top (required)>' >>>> 13. >>>> >>>> remote: from /usr/lib64/ruby/1.9.1/rubygems/custom_require.rb:36:in >>>> `require' >>>> 14. >>>> >>>> remote: from /usr/lib64/ruby/1.9.1/rubygems/custom_require.rb:36:in >>>> `require' >>>> 15. >>>> >>>> remote: error: hook declined to update refs/heads/dev >>>> 16. >>>> >>>> To /home/git/repositories/risk/risk.git >>>> 17. >>>> >>>> ! [remote rejected] dev -> dev (hook declined) >>>> 18. >>>> >>>> error: failed to push some refs to '/home/git/repositories/risk/r >>>> isk.git' >>>> >>>> -- >>> You received this message because you are subscribed to the Google >>> Groups "GitLab" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To view this discussion on the web visit https://groups.google.com/d/ >>> msgid/gitlabhq/fdc516e1-aadc-4867-b8a2-33771937ed86%40googlegroups.com >>> <https://groups.google.com/d/msgid/gitlabhq/fdc516e1-aadc-4867-b8a2-33771937ed86%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> (\_ /) copy the bunny to your profile >> (0.o ) to help him achieve world domination. >> (> <) come join the dark side. >> /_|_\ (we have cookies.) >> > -- > You received this message because you are subscribed to the Google Groups > "GitLab" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/gitlabhq/4dcb5e05-a5cd-409b-8c65-8b834c991fb8%40googlegroups.com > <https://groups.google.com/d/msgid/gitlabhq/4dcb5e05-a5cd-409b-8c65-8b834c991fb8%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- (\_ /) copy the bunny to your profile (0.o ) to help him achieve world domination. (> <) come join the dark side. /_|_\ (we have cookies.) -- You received this message because you are subscribed to the Google Groups "GitLab" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/CALEK4Ppa2HULAcpi9BXZ7PxZGGwhDoTsiBH2rksZA74YUgg0xg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
