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

Closed
Open
Created Mar 03, 2013 by Administrator@rootOwner

gentoo 4.2 repo generation problem [Solved]

Created by: 666threesixes666

latest ruby, mysql 5.1, python 3&2.7, apache + passenger, latest git. i can login, and create project, but it shows the commands to make the repo rather than running them. it keeps thinking that its got a read write permission error. im absolutely positive gitlab is in git and git is in gitlab. i fix all the config things except for the latest init script as i cannot touch it, and sidekiq....

as user gitlab i can do most of the commands except for when it comes up to the 2nd to last one, then it starts trying to cd existing repo. the git machine and i do not have connectivity at the moment so ill post exact details later. git init (not git init --bare) is run. ssh keys are installed and thats fine. gitolite is gitlab style, not gentoo or gitolite style.

looking at sidekiq it looks rather important, the rest of the configuration check checks out fine for the most part....

Assignee
Assign to
Time tracking