|Deletions are marked like this.||Additions are marked like this.|
|Line 51:||Line 51:|
|Gitlab 11.10.8 is available in experimental (many open security issues). Use libjs-uglify from unstable.||Gitlab 11.11.7 is available in experimental (no open security issues). Use libjs-uglify from unstable.|
|Line 53:||Line 53:|
|libgit2 transition is delaying upload to unstable. grpc and protobuf updates are delaying 11.11.7 in experimental.||libgit2, grpc and protobuf transition is delaying upload to unstable.|
|Line 57:||Line 57:|
|# apt -t experimental install gitlab
Or use second option via aptitude
# aptitude -t experimental install gitlab
|# apt -t experimental install ruby-rugged ruby-grpc ruby-google-protobuf
# apt -t experimental install gitlab-workhorse ruby-devise ruby-task-list ruby-bootstrap-form ruby-httparty ruby-sshkey gitaly
# apt install gitlab/experimental
Gitlab is a git front end with repository management, graphs, links, goodies, commands to run, and review capabilities similar in feel to a self hosted github.
Debian is running its own Instance of Gitlab under https://salsa.debian.org, which is not based on the packaged version.
See this proposal to create a fasttrack repo for packages like gitlab.
Gitlab 11.11.7 is available in personal repo of gitlab maintainer targeting buster as base distribution. (no open security issues).
Add to /etc/apt/sources.list
deb https://deb.debian.org/debian buster-backports contrib main deb https://people.debian.org/~praveen/gitlab buster-backports contrib main deb https://people.debian.org/~praveen/gitlab buster-fasttrack contrib main
# apt update
You may encounter the following error message:
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0B76920762A6B785
If so, those commands can help:
# wget https://people.debian.org/~praveen/gitlab/praveen.key.asc # apt-key add praveen.key.asc
# apt -t buster-backports install gitlab
Note: https://gitlab.debian.net is running on this version.
Unstable (be careful when updating packages)
Gitlab 11.8.10 is available in unstable (many open security issues). Note: Use experimental till libgit2 transition is complete.
# apt install gitlab
We try to keep the version in unstable in a good shape with latest security updates, but some times dependency updates breaks gitlab.
Experimental - During freeze and transitions
Gitlab 11.11.7 is available in experimental (no open security issues). Use libjs-uglify from unstable.
libgit2, grpc and protobuf transition is delaying upload to unstable.
# apt install libjs-uglify/unstable # apt -t experimental install ruby-rugged ruby-grpc ruby-google-protobuf # apt -t experimental install gitlab-workhorse ruby-devise ruby-task-list ruby-bootstrap-form ruby-httparty ruby-sshkey gitaly # apt install gitlab/experimental
Stretch Backports (upgrade to buster)
Gitlab 11.4.9 is available in stretch-backports (still affected by some security issues, many security releases behind).
Gitlab 11.5.10 is available for stretch-backports via personal repo of gitlab maintainer (many security releases behind) from https://people.debian.org/~praveen/gitlab
Add to /etc/apt/sources.list
deb https://people.debian.org/~praveen/gitlab stretch-backports contrib main
Note 1: Official stretch-backports repo is also required for this personal repo to work. See Backports. You will also need contrib section
# apt -t stretch-backports install gitlab
It is recommended to upgrade to buster to receive security updates.
Note: Remove unnecessary packages after upgrade (remove ruby-bootsnap if you see strange load errors).
# apt remove rails npm ruby-bootsnap
Stretch (upgrade to stretch backports and then to buster)
Gitlab 8.13.11 is available in stretch, but it is not receiving any security updates. So it is recommend to update to newer versions from unstable or buster or stretch-backports.
# apt install gitlab
It is recommended to upgrade to stretch backports and then to buster to receive security updates.
You can reach the maintainers of gitlab package via Matrix at #debian-gitlab:poddery.com. Join via your browser if you don't have a matrix account.
Installing gitlab on an lxc container to test - See gitlab/lxc
Updating gitlab package to newer versions - See Teams/Ruby/Packaging/newUpstreamRailsApp
- Aim to get gitlab back in main by bullseye release by packaging all node dependencies. We can do this gradually starting with webpack from the archive.
- Get autopkgtest working so we can detect problems when someone updates dependencies without coordinating with us.
Note: this section is about installation of upstream-provided unofficial packages.
all actions are performed under root user, in ~ unless otherwise noted.
navigate to https://www.gitlab.com/downloads/ and copy down the link to the debian deb package.
as of this writing @ june, 5, 2014
- dpkg -i gitlab*
i got errors 1st time around 2nd time around gitlab looked like it set everything and ran well.
To avoid errors, execute /opt/gitlab/embedded/bin/runsvdir-start for one minute, more or less (tested in 7.9.0 and 7.9.1 omnibus versions).
- gitlab-ctl reconfigure
to verify that things are running
- gitlab-ctl status
navigate to your servers ip address or domain name, and login as:
user: root password: 5iveL!fe