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

Closed
Open
Created Dec 27, 2013 by Administrator@rootOwner

An error occurred while installing gon (4.1.1), and Bundler cannot continue

Created by: ShahimEssaid

I'm trying to install tag v6.4.3 according to the instructions but I get the following error.

Using gitlab_omniauth-ldap (1.0.3)

ArgumentError: wrong number of arguments (1 for 0) An error occurred while installing gon (4.1.1), and Bundler cannot continue. Make sure that gem install gon -v '4.1.1' succeeds before bundling.

when I run:

root@public:/home/git/gitlab# sudo -u git -H bundle install --deployment --without development test mysql aws

This is on Ubuntu 12.04.3 64 bits with the default Ubuntu Ruby/gem:

root@public:/home/git/gitlab# ruby --version ruby 1.9.3p0 (2011-10-30 revision 33570) [x86_64-linux] root@public:/home/git/gitlab# gem --version 1.8.11

A couple of possibly relevant things are that I am doin this in an LXC container and on the first try I had a root UMASK of 057 so there were permission problems with the installed gems but I manually cleaned that up and was able to make progress to this point. I'll try on a new Ubuntu install in virtualbox to see if it is a problem with my current Ubuntu LXC install.

Assignee
Assign to
Time tracking