Hello the list,

I am trying to follow the instructions at 
https://gitlab.com/gitlab-org/gitlab-ee/blob/master/doc/update/8.7-ce-to-ee.md 
to upgrade our GitLab CE server to GitLab EE

Server is CentOS 6.7, with GitLab CE originally installed by 
$ curl 
https://packages.gitlab.com/install/repositories/gitlab/gitlab-ce/script.rpm.sh 
| sudo bash
$ sudo yum install gitlab-ce
And the current version is
$ rpm -q gitlab-ce
gitlab-ce-8.7.5-ce.0.el6.x86_64

I follow the steps from the guide linked above
$ cd /home/git/gitlab
$ sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production
Which gives the error message
sudo: bundle: command not found

I am aware of this problem from earlier work, and have seen the advice at 
https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/doc/maintenance/README.md#invoking-rake-tasks
However the *gitlab-rake* command will work for the step above, but will 
not cover all the steps needed in this guide. Specifcally it does not seem 
that it will work for
$ sudo -u git -H bundle install --without postgres development test 
--deployment

I have considered updating the $PATH variable, or specifying a full path to 
the *bundle* command, but am at a loss there, because there are so many to 
choose from! The rpm alone seems to have installed *bundle* into 7 
different directories, and I have no idea which one to use. All told I seem 
to have a choice among 19 *bundle* commands:
$ sudo find / -type f  -name bundle
/opt/vagrant/embedded/gems/gems/bundler-1.10.5/lib/bundler/man/bundle
/opt/vagrant/embedded/gems/gems/bundler-1.10.5/bin/bundle
/opt/vagrant/embedded/gems/bin/bundle
/opt/gitlab/embedded/service/gitlab-rails/bin/bundle
/opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/omniauth-auth0-1.4.1/examples/ruby-on-rails-webapp/bin/bundle
/opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/railties-4.2.6/lib/rails/generators/rails/app/templates/bin/bundle
/opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/devise-3.5.4/test/rails_app/bin/bundle
/opt/gitlab/embedded/lib/ruby/gems/2.1.0/gems/bundler-1.10.6/lib/bundler/man/bundle
/opt/gitlab/embedded/lib/ruby/gems/2.1.0/gems/bundler-1.10.6/bin/bundle
/opt/gitlab/embedded/bin/bundle
/home/git/gitlab/bin/bundle
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/rails-4.1.12/guides/code/getting_started/bin/bundle
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/railties-4.1.12/lib/rails/generators/rails/app/templates/bin/bundle
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/devise-3.5.2/test/rails_app/bin/bundle
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/sass-rails-4.0.5/test/fixtures/engine_project/test/dummy/bin/bundle
/home/git/tools/ruby/lib/ruby/gems/2.1.0/gems/bundler-1.11.0/lib/bundler/man/bundle
/home/git/tools/ruby/lib/ruby/gems/2.1.0/gems/bundler-1.11.0/exe/bundle
/home/git/tools/ruby/lib/ruby/gems/2.1.0/gems/railties-4.2.5/lib/rails/generators/rails/app/templates/bin/bundle
/home/git/tools/ruby/bin/bundle

Which comes down to one question: which "bundle" command should I use when 
to steps tell me to "sudo -u git -H bundle install ...."?

Thank you for reading this far, and for any help you can offer

-- 
Alan

-- 
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 gitlabhq+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/gitlabhq/c65e1fcd-ca41-4767-8167-cd6782b3b4ad%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to