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

Closed
Open
Created May 07, 2012 by Administrator@rootOwner

Bash path (FreeBSD)

Created by: voidzero

Hi,

While I do realise that gitlab does not "support FreeBSD officially", I have set it up on my FreeBSD system yesterday and it works perfectly fine. The instructions in installation.md are fine and any FreeBSD user can probably decide how the commands should be for them. As a trivial aside I would prefer it if you would remove the sudo stuff and just prefix the commands with the proper username. But lest I digress back to the issue at hand.

I have only found one issue that, due to its nature, took forever to hunt down. After each push I kept seeing the following error:

remote: error: cannot run hooks/post-receive: No such file or directory

Finally I traced it down: it's because the files in lib/hooks contain the #!/bin/bash shebang, but FreeBSD hasn't this by default. Perhaps you could either set the shebang to #!/bin/sh if it is possible or else to '#!/usr/bin/env bash'

Now that I found this issue I couldn't help but smirk. Please consider this issue.

Assignee
Assign to
Time tracking