Gentoo Packages

Starting with version 18.4.0 GitLab needs another PG extension: amchek. To list the current PG extensions run as the PG admin user:

psql -d <your GitLab DB> -c "\dx"

To create the extensions if they are missing do:

psql -d template1 -c "CREATE EXTENSION IF NOT EXISTS amcheck;"
psql -d template1 -c "CREATE EXTENSION IF NOT EXISTS pg_trgm;"
psql -d template1 -c "CREATE EXTENSION IF NOT EXISTS btree_gist;"
psql -d template1 -c "CREATE EXTENSION IF NOT EXISTS plpgsql;"

With version 18.3.0 upstream decided to "Deprecate the ability to use an arbitrary Git installation in favor of bundled Git" (see https://gitlab.com/gitlab-org/gitaly/-/issues/6725).

So I removed the gitaly_git use flag (was active by default) and only support the bundled Git from now on.

Note, though, that this first of all applies to the Gitaly part of GitLab (that, as I understand it, will now always use the bundled Git) and you could still change the 'bin_path' setting in /etc/gitlab/gitlab.yml to use /usr/bin/git of the Gentoo Git package for the other parts of GitLab instead. But upstream recommends:

You should use the Git version provided by Gitaly that:

• Is always at the version required by GitLab.
• May contain custom patches required for proper operation.

One of the breaking changes with upcoming release 18.0 is: Postgres 14/15 deprecated Since version 17.0 Postgres 16 is already supported but with version 18.0 failing to upgrade to Postgres 16 will break the deployment.

In the upcomming version 18.0 the PostgreSQL dependency will be changed to "dev-db/postgresql:16" so the emerge will pull in the new slot 16 of dev-db/postgresql. If only the postgresql client is installed on the local host (USE flag -server) the ebuild will do "eselect postgresql set 16" before building GitLab (Note that you have to update postgresql on you database server beforehand!). If the postgresql server is running on the local host the ebuild will terminate and ask you to upgrade postgresql first.