Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #5996

Closed
Open
Created Jan 07, 2014 by Administrator@rootOwner

Gitlab 6.4 upgrade guide broken

Created by: jacobkiers

Hi all,

I've been using Gitlab (on Ubuntu 12.10) to full satisfaction for the past year or so. However, when I tried to upgrade to version 6.4-stable using the guide, that failed. As I'm totally unexperienced with Ruby and the Ruby ecosystem, that was a nasty surprise.

My question to you is to try not to include "breaking changes" anymore, or at least update the guide or CHANGELOG to reflect that (so that we as users can make an informed decision).

Hereafter I would like to tell you the tale of how I managed upgrading anyway (remember: as someone almost without any experience with Ruby).

However, when I tried to upgrade using the 6.3 => 6.4 upgrade guide, I got an error when running the following command: sudo -u git -H bundle install --without development test postgres --deployment

Bundler could not find compatible versions for gem "bundler":
  In Gemfile:
    rails (~> 4.0.0) ruby depends on
      bundler (< 2.0, >= 1.3.0) ruby

  Current Bundler version:
    bundler (1.2.3)

This Gemfile requires a different version of Bundler.
Perhaps you need to update Bundler by running `gem install bundler`?

That was a real nasty surprise, especially as I'm not that experienced with Ruby.

Then I tried installing using the --no-deployment flag, which gave me the following error message:

Bundler could not find compatible versions for gem "bundler":
  In Gemfile:
    rails (~> 4.0.0) ruby depends on
      bundler (< 2.0, >= 1.3.0) ruby

  Current Bundler version:
    bundler (1.2.3)

This Gemfile requires a different version of Bundler.
Perhaps you need to update Bundler by running `gem install bundler`?

To fix that, I had to run sudo gem install bundler.

Then I re-tried running the installer (again with the --no-deployment flag: sudo -u git -H bundle install --without development test postgres --no-deployment), which gave me another error again:

Fetching source index from https://rubygems.org/
Resolving dependencies..........................................................................................................


Your user account isn't allowed to install to the system Rubygems.
You can cancel this installation and run:

    bundle install --path vendor/bundle

to install the gems into ./vendor/bundle/, or you can enter your password
and install the bundled gems to Rubygems using sudo.

Password:
SystemExit: exit

An error occurred while installing rake (10.1.0), and Bundler cannot continue.
Make sure that `gem install rake -v '10.1.0'` succeeds before bundling.

So finally, I tried it as follows: sudo -u git -H bundle install --without development test postgres --no-deployment --path vendor/bundle, which successfully installed the bundle.

Finally, I ran the original command again, which then gave no errors anymore (sudo -u git -H bundle install --without development test postgres --deployment). That went fine.

As you can see, this was quite an adventure for me 😄

Assignee
Assign to
Time tracking