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
  • #5593

Closed
Open
Created 11 years ago by Administrator@rootOwner
  • New issue

  • Report abuse

  • New issue

  • Report abuse

following install docs on ubuntu 13.10 bundle install fails (rubygems version)

Closed

following install docs on ubuntu 13.10 bundle install fails (rubygems version)

Created by: karlhungus

Get a message

{22:24}~/gitlab/gitlab:master ✓ ➭ bundle install --without postgres aws
Fetching source index from https://rubygems.org/
Installing rake (10.1.0) 
Errno::EACCES: Permission denied - /usr/local/lib/ruby/gems/2.0.0/build_info/rake-10.1.0.info
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.

Running these commands seem fixes the issue (may want to note this in the docs)

gem install rubygems-update
update_rubygems
gem update --system

Leached from here: http://stackoverflow.com/questions/13626143/how-to-upgrade-rubygems, which was pointed out here: https://github.com/bundler/bundler/issues/2445

Might due to include this docs here: https://github.com/gitlabhq/gitlabhq/blob/master/doc/install/installation.md#install-gems, this isn't really a gitlab problem, but it may frustrate potential users, of course it should proably be removed if rubygems version is greater than 2.1.9

Linked issues
...

    Related merge requests

    • Administrator
      Administrator @root · 11 years ago
      Owner

      Created by: jvanbaarsen

      @karlhungus Is this still an issue? /cc @Razer6 (Sorry for all the cc's 😄 )

      By Administrator on 2014-01-10T22:47:13 (imported from GitLab project)

    • Administrator
      Administrator @root · 11 years ago
      Owner

      Created by: Razer6

      It's been at least 2 weeks (and a new release) since we heard from you. I'm closing this issue but if you still experience this problem, please open a new issue (but also reference the old issue(s)). Make sure to also include the necessary debugging information conforming to the issue tracker guidelines found in our contributing guidelines.

      By Administrator on 2014-02-09T18:19:35 (imported from GitLab project)

    • You're only seeing other activity in the feed. To add a comment, switch to one of the following options.
    Please register or sign in to reply
    0 Assignees
    Assign to
    Milestone
    No milestone
    None
    None
    Time tracking
    Due date
    None
    None
    0
    Labels
    None
    Assign labels
    • No matching results
    • Manage project labels
    Confidentiality
    Not confidential

    You are going to turn on confidentiality. Only team members with at least Reporter access will be able to see and leave comments on the issue.

    Lock issue
    Unlocked
    participants
    Reference: