===> The following configuration options are available for gitlab-ce-16.10.2_2:
KERBEROS=on: Kerberos support
===> Use 'make config' to modify these settings
Gitlab was installed successfully.
You now need to set up the various components of Gitlab, so please
follow the instructions in the guide at:
https://gitlab.fechner.net/mfechner/Gitlab-docu/blob/master/install/16.10-freebsd.md
If upgrading from < 11.9.7:
!! WARNING: Please make sure you read in UPDATING entry 20190423 !!
If upgrading
If you just installed an major upgrade of GitLab, for example you
switched from 14.5.x to 14.6.x, please follow the instructions in the guide at:
https://gitlab.fechner.net/mfechner/Gitlab-docu/blob/master/update/16.9-16.10-freebsd.md
If you just installed an minor upgrade of GitLab please follow
the instructions in the guide at:
https://gitlab.fechner.net/mfechner/Gitlab-docu/blob/master/update/freebsd_patch_versions.md
Reason:
With the upgrade to version 16.11 the default path for gitlab-ce changed:
/usr/local/www/gitlab-ce -> /usr/local/www/gitlab
Make sure you follow the upgrade manual very carefully:
https://gitlab.fechner.net/mfechner/Gitlab-docu/-/blob/master/update/16.10-16.11-freebsd.md
The gitlab port also got a new flavor gitlab@ee to make the Gitlab
Enterprise Edition available (you will need a license for it).
Please note, that the ee flavor is a draft, but any feedback is welcome.
See also the installation and upgrade manual for more details.
https://gitlab.fechner.net/mfechner/Gitlab-docu/-/blob/master/install/16.11-freebsd.md
Reason:
Before you upgrade to version 16.4.x or higher, make sure you did the
upgrade to 16.3.x!
The database migration for 16.4.1 can fail due to unexpected name of a foreign key.
So it is recommended to have a database backup available in case the solution
described in the update manual does not work for you.
The upgrade manual can be found as usual here:
https://gitlab.fechner.net/mfechner/Gitlab-docu/-/blob/master/update/16.3-16.4-freebsd.md
2021-06-21
Affects: users of www/gitlab-ce
Author: mfechner@FreeBSD.org
Reason:
The upgrade of Gitlab 14.0.0 is in preparation.
You must upgrade first to 13.12.
For more information see here:
https://about.gitlab.com/blog/2021/06/04/gitlab-moving-to-14-breaking-changes/
To do the upgrade, make sure you follow the upgrade manuals:
https://gitlab.fechner.net/mfechner/Gitlab-docu/-/tree/master/update
I will merge the 14.0.0 upgrade later to quarterly branch to give you
some time for the upgrade to 13.12.
www/gitlab-ce: Update RUN_DEPENDS
- Change RUN_DEPENDS from rubygem-bootsnap to rubygem-bootsnap117
- Change RUN_DEPENDS from rubygem-google-apis-core to
rubygem-google-apis-core011
- Change RUN_DEPENDS from rubygem-google-cloud-storage to
rubygem-google-cloud-storage145
- Bump PORTREVISION for dependency change
www/gitlab-ce: use sidekiq from ports
The vendored sidekiq version does pollute the build environment, as
it does not respect the STAGEDIR.
As the vendored gem is maybe only a temporary solution:
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/142986
till these changes are fixed upstream, I will switch back to
the sidekiq 7.1.6 version provided via ports.
www/gitlab-ce: CRITICAL security update to 16.7.2 and bugfixes
This update fixes a CVE scored with 10.0:
CVE-2023-7028 (Account Takeover via Password Reset without user interactions)
You maybe want to stop you gitlab instance till you have that update installed.
More details can be found here:
https://about.gitlab.com/releases/2024/01/11/critical-security-release-gitlab-16-7-2-released/
Security: 4c8c2218-b120-11ee-90ec-001b217b3468
www/gitlab-ce: fix database migration error
Database migration step requires vite_ruby 3.3 even if a higher version is
allowed.
Following error is fixed:
E, [2023-12-14T14:15:11.286071 #1116] ERROR -- : Failed to check mode for Vite:
vite-plugin-ruby@^3.2.2 might not be compatible with vite_ruby-3.5.0
You may disable this check if needed:
https://vite-ruby.netlify.app/config/#skipcompatibilitycheck
You may upgrade both by running:
bundle exec vite upgrade
rake aborted!
ArgumentError: vite-plugin-ruby@^3.2.2 might not be compatible with
vite_ruby-3.5.0
You may disable this check if needed:
https://vite-ruby.netlify.app/config/#skipcompatibilitycheck
You may upgrade both by running:
bundle exec vite upgrade
/usr/local/www/gitlab-ce/config/environment.rb:7:in `<top (required)>'
<internal:/usr/local/lib/ruby/site_ruby/3.1/rubygems/core_ext/kernel_require.rb>:38:in
`require'
<internal:/usr/local/lib/ruby/site_ruby/3.1/rubygems/core_ext/kernel_require.rb>:38:in
`require'
Tasks: TOP => db:migrate => db:load_config => environment
(See full trace by running task with --trace)
www/gitlab-ce: use update patch if not already updated to 16.6.0/1
The patch was updated, so use it if you have not already used the previous one.
This is required as the old version cannot be downloaded anymore.
If you have already upgraded to 16.6.1, this patch can be ignored.
This is also the reason why I do not bump the version.
www/gitlab-ce: fix build problem due to dependency change
Relaxe the version restriction for aws-sdk-s3.
This fixes regression from 69027ee7a067d387ebc78fdfae2be8aec385330a
www/gitlab-ce: Fix Gemfile
The (similar) fix for Gemfile was already committed [1] but being removed later
during gitlab-ce updates.
(cd /wrkdirs/usr/ports/www/gitlab-ce/work/gitlab-foss-v16.5.1 && /bin/rm -f
Gemfile.lock && bundle install --local)
Don't run Bundler as root. Installing your bundle as root will break this
application for all non-root users on this machine.
Could not find gem 'aws-sdk-core (~> 3.185.1)' in cached gems or installed
locally.
The source contains the following gems matching 'aws-sdk-core':
* aws-sdk-core-3.186.0
*** Error code 7
Reference: https://cgit.freebsd.org/ports/commit/www/gitlab-ce?id=cd3ccf5407757430ac5899a4ba0fecd61992a431
[1]
www/gitlab-ce: Fix Gemfile to match RUN_DEPENDS
The error message is as follows:
cp -f
/wrkdirs/usr/ports/www/gitlab-ce/work/gitlab-foss-v16.5.0/config/database.yml.postgresql
/wrkdirs/usr/ports/www/gitlab-ce/work/gitlab-foss-v16.5.0/config/database.yml.sample
(cd /wrkdirs/usr/ports/www/gitlab-ce/work/gitlab-foss-v16.5.0 && /bin/rm -f
Gemfile.lock && bundle install --local)
Don't run Bundler as root. Installing your bundle as root will break this
application for all non-root users on this machine.
Could not find gem 'grpc (~> 1.58.0)' in cached gems or installed locally.
The source contains the following gems matching 'grpc':
* grpc-1.59.0
*** Error code 7
Approved by: portmgr (blanket)
www/gitlab-ce: Update RUN_DEPENDS
- Change RUN_DEPENDS from rubygem-carrierwave to rubygem-carrierwave1
- Change RUN_DEPENDS from rubygem-fugit to rubygem-fugit18
- Change RUN_DEPENDS from rubygem-rouge to rubygem-rouge41
- Bump PORTREVISION for dependency change
www/gitlab-ce: Allow run with rubygem-sidekiq6 6.5.12
- Bump PORTREVISION for package change
Note that it is an upstream issue.
Upstream has conflicting requirement for sidekiq which causes runtime issue.
from Gemfile:
gem 'sidekiq', '~> 6.5.7'
from lib/gitlab/patch/sidekiq_cron_poller.rb:
if Gem::Version.new(Sidekiq::VERSION) != Gem::Version.new('6.5.7')
raise 'New version of sidekiq detected, please remove or update this patch'
end
www/gitlab-ce: mark public/robots.txt as a configuration file
this allows users to modify it and it will not be overwritten
with a new upgrade of gitlab.
www/gitlab-ce: Allow run with rubygem-sidekiq6 6.5.11
- Bump PORTREVISION for package change
Note that it is an upstream issue.
Upstream has conflicting requirement for sidekiq which causes runtime issue.
from Gemfile:
gem 'sidekiq', '~> 6.5.7'
from lib/gitlab/patch/sidekiq_cron_poller.rb:
if Gem::Version.new(Sidekiq::VERSION) != Gem::Version.new('6.5.7')
raise 'New version of sidekiq detected, please remove or update this patch'
end
www/gitlab-ce: upgrade to 16.4.1
At first make sure you finished the upgrade to 16.3.x!
While running the database migration step, an error can happen.
So maybe test this at first in a test instance and/or have a backup ready.
You should not need it, but for this update it is better to have it ;)
A fix is described in the upgrade manual:
https://gitlab.fechner.net/mfechner/Gitlab-docu/-/blob/master/update/16.3-16.4-freebsd.md#database-migration-fails
The problem itself is described here:
https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/8227
But as everyone has a different name for the foreign key that causes this
problem
a corrected migration step does maybe not fix the problem for all users.
(Only the first 15 lines of the commit message are shown above )
www/gitlab-ce: Update RUN_DEPENDS
- Change RUN_DEPENDS from rubygem-semver_dialects to rubygem-semver_dialects12
- Change RUN_DEPENDS from rubygem-state_machines-activerecord to
rubygem-state_machines-activerecord08
- Bump PORTREVISION for dependency change
www/gitlab-ce: fix dependency for mail/rubygem-premailer-rails-rails70
Gitlab requires version 1.10.x but it was upgraded in commit:
2c43076cf5bfbd0ad7dc5789e4fcfb19013b9511
to 1.12.0
www/gitlab-ce: Change RUN_DEPENDS from rubygem-aws-sdk-core to
rubygem-aws-sdk-core3175
- Update version requirement of RUN_DEPENDS
- Bump PORTREVISION for dependency change
bsd.sites.mk: Update all ports using USE_GITLAB
Replace GL_COMMIT by GL_TAGNAME in all ports. The new GL_TAGNAME is
backwards-compatible (accepting any commit hash as before), but also
understands an actual tag name. Moving to tag names where appropriate is
left to individual ports' maintainers.
Approved by: portmgr (tcberner, mentor)
Differential Revision: https://reviews.freebsd.org/D37077
www/gitlab-ce: Update RUN_DEPENDS
- Change RUN_DEPENDS from rubygem-aws-sdk-s3 to rubygem-aws-sdk-s31122
- Change RUN_DEPENDS from rubygem-nokogiri to rubygem-nokogiri114
- Change RUN_DEPENDS from rubygem-rack227 to rubygem-rack22
- Bump PORTREVISION for dependency change
www/gitlab-ce: Update RUN_DEPENDS
- Change RUN_DEPENDS from rubygem-octokit to rubygem-octokit5
- Change RUN_DEPENDS from rubygem-ohai to rubygem-ohai17
- Bump PORTREVISION for dependency change
www/gitlab-ce: Update RUN_DEPENDS
- Change RUN_DEPENDS from rubygem-aws-sdk-core to rubygem-aws-sdk-core3171
- Change RUN_DEPENDS from rubygem-google-protobuf to rubygem-google-protobuf322
- Change RUN_DEPENDS from rubygem-loofah to rubygem-loofah220
- Change RUN_DEPENDS from rubygem-oj to rubygem-oj313
- Bump PORTREVISION for dependency change
textproc/rubygem-semver_dialects: Remove duplicate
Same port existed in the tree under devel/rubygem-semver_dialects.
- Update www/gitlab-ce to reflect to the older port in the tree
- Add enttry into MOVED
Approved by: portmgr (just-fix-it)
