===> The following configuration options are available for gitlab-ce-19.4.2_1:
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.com/mfechner/freebsd-gitlab-docu/blob/master/install/19.4-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 18.6.x to 18.7.x, please follow the instructions in the guide at:
https://gitlab.com/mfechner/freebsd-gitlab-docu/blob/master/update/19.3-19.4-freebsd.md
If you just installed an minor upgrade of GitLab please follow
the instructions in the guide at:
https://gitlab.com/mfechner/freebsd-gitlab-docu/blob/master/update/freebsd_patch_versions.md
Reason:
Make sure you compare your /usr/local/www/gitlab/config/puma.rb with
/usr/local/www/gitlab/config/puma.rb.sample and make sure you have the:
require "logger"
line in your puma.rb.
This fixes an error:
/usr/local/lib/ruby/gems/3.2/gems/activesupport-7.0.8.7/lib/active_support/logger_thread_safe_level.rb:12:in `<module:LoggerThreadSafeLevel>': uninitialized constant ActiveSupport::LoggerThreadSafeLevel::Logger (NameError)
Logger::Severity.constants.each do |severity|
Reason:
Make sure you upgrade first to 16.11.x before you upgrade to the today
released version 17.0.0.
For more details see:
https://gitlab.fechner.net/mfechner/Gitlab-docu/-/blob/master/update/16.11-17.0-freebsd.md
www/gitlab: fix regression from 40d54199a8b5b902f127d6f3db01ecc250586dc3
Relaxe redis dependency, regarding the redis changelog, there is no
breaking change in the new version.
As the redis gem is also used by rails it does not make sense to
duplicate the complete rails ports for gitlab.
www/gitlab: fix error uninitialized constant
ActiveSupport::LoggerThreadSafeLevel::Logger
The upgrade of gem concurrent-ruby to 1.3.5 made a bug in activesupport visible.
The bug seems to be fixed for rails 7.1 and 7.2 but not 7.0 which gitlab uses.
https://github.com/rails/rails/pull/49372https://github.com/rails/rails/issues/54260
So we import the Logger to fix the error message:
bundler: failed to load command: puma (/usr/local/bin/puma)
/usr/local/lib/ruby/gems/3.2/gems/activesupport-7.0.8.7/lib/active_support/logger_thread_safe_level.rb:12:in
`<module:LoggerThreadSafeLevel>': uninitialized constant
ActiveSupport::LoggerThreadSafeLevel::Logger (NameError)
Logger::Severity.constants.each do |severity|
^^^^^^^^^^
from
/usr/local/lib/ruby/gems/3.2/gems/activesupport-7.0.8.7/lib/active_support/logger_thread_safe_level.rb:9:in
`<module:ActiveSupport>'
from
/usr/local/lib/ruby/gems/3.2/gems/activesupport-7.0.8.7/lib/active_support/logger_thread_safe_level.rb:8:in
`<top (required)>'
(Only the first 15 lines of the commit message are shown above )
www/gitlab: make it possible to define the log level of gitlab
For only warnings, just execute:
sysrc gitlab_log_level="warn"
and restart gitlab:
service gitlab restart
Possible values are:
debug
info
warn
error
www/gitlab: fix regression from 001ec8e60d233781c71246f5434306c06cafb453
Error message:
===> gitlab-ce-17.7.0 depends on package: rubygem-rexml>=3.3.2<3.4 - not found
Make rubygem-rexml version 3.3 available for a specific port for gitlab.
devel/rubygem-licensee: fix another conflict with faraday
further isolation ports required for gitlab to work around update by
335fc7c38d61142727cb9f01fd9e401c476e4ad8
This should fix the problem if the two ports are installed:
sysutils/rubygem-vagrant_cloud
devel/rubygem-licensee
PR: 283073
www/gitlab: fix deeper regression from 8a2d8fae15f9c9986ad48a54e36ad58635c85cb4
Seperate the ports a little bit more.
Patch was mostly provided by sunpoet.
www/gitlab: fix regression from 335fc7c38d61142727cb9f01fd9e401c476e4ad8
Gitlab requires net-http 0.4.1:
Because faraday >= 2, < 2.5 could not be found in locally installed gems
and faraday >= 2.5, < 2.12.1 could not be found in locally installed gems,
faraday >= 2, < 2.12.1 cannot be used.
And because faraday >= 2.12.1 depends on faraday-net_http >= 2.0, < 3.5,
faraday >= 2 requires faraday-net_http >= 2.0, < 3.5.
Because faraday-net_http >= 3.4.0 depends on net-http >= 0.5.0
and faraday-net_http >= 2.0, < 3.4.0 could not be found in locally installed
gems,
faraday-net_http >= 2.0 requires net-http >= 0.5.0.
Thus, faraday >= 2 requires net-http >= 0.5.0.
So, because Gemfile depends on faraday ~> 2
and Gemfile depends on net-http = 0.4.1,
version solving has failed.
While fixing the problem, moved gitlab used packages to own package names with a
PKGNAMESUFFIX of `-gitlab`.
This should make the gitlab package much more stable if updates in the ports are
done.
www/gitlab: Update RUN_DEPENDS
- Change RUN_DEPENDS from rubygem-json to rubygem-json27
- Change RUN_DEPENDS from rubygem-net-http to rubygem-net-http041
- Bump PORTREVISION for dependency change
www/gitlab: fix regression from 372f5ebfd99a96b7060145c632e350b5870b8c7d
===> gitlab-ce-17.5.1_1 depends on package: rubygem-webrick>=1.8.1<1.9 - not
found
*** Error code 1
www/gitlab: fix regression from 0cd77d5e59481973c44a127c62331d8ff41350f8
Sprockets detected. This patch can likely be removed."}
bundler: failed to load command: puma (/usr/local/bin/puma)
/usr/local/www/gitlab/config/initializers/sprockets_patch.rb:12:in `<top
(required)>': New version of Sprockets detected. This patch can likely be
removed. (RuntimeError)
from
/usr/local/lib/ruby/gems/3.2/gems/railties-7.0.8.4/lib/rails/engine.rb:667:in
`load'
from
/usr/local/lib/ruby/gems/3.2/gems/railties-7.0.8.4/lib/rails/engine.rb:667:in
`block in load_config_initializer'
from
/usr/local/lib/ruby/gems/3.2/gems/activesupport-7.0.8.4/lib/active_support/notifications.rb:208:in
`instrument'
from
/usr/local/lib/ruby/gems/3.2/gems/railties-7.0.8.4/lib/rails/engine.rb:666:in
`load_config_initializer'
from
/usr/local/lib/ruby/gems/3.2/gems/railties-7.0.8.4/lib/rails/engine.rb:620:in
`block (2 levels) in <class:Engine>'
from
/usr/local/lib/ruby/gems/3.2/gems/railties-7.0.8.4/lib/rails/engine.rb:619:in
`each'
from
/usr/local/lib/ruby/gems/3.2/gems/railties-7.0.8.4/lib/rails/engine.rb:619:in
`block in <class:Engine>'
from
/usr/local/lib/ruby/gems/3.2/gems/railties-7.0.8.4/lib/rails/initializable.rb:32:in
`instance_exec'
from
/usr/local/lib/ruby/gems/3.2/gems/railties-7.0.8.4/lib/rails/initializable.rb:32:in
`run'
from
/usr/local/lib/ruby/gems/3.2/gems/railties-7.0.8.4/lib/rails/initializable.rb:61:in
`block in run_initializers'
(Only the first 15 lines of the commit message are shown above )
www/gitlab: update to 17.3.3
Added a unique PORTREVISION tag to be in sync with all gitlab related ports.
Please increase in www/gitlab/Makefile.common GITLAB_PORTREVISION if required.
www/gitlab: Update RUN_DEPENDS
- Change RUN_DEPENDS from rubygem-google-cloud-storage_transfer to
rubygem-google-cloud-storage_transfer12
- Change RUN_DEPENDS from rubygem-redis to rubygem-redis52
- Change RUN_DEPENDS from rubygem-redis-clustering to rubygem-redis-clustering52
- Bump PORTREVISION for dependency change
www/gitlab: fix regression from 09d7eada6c2c214adac9780307f2dd7689ab8660
Gitlab requires cssbundling 1.4.0.
As changelog of cssbundling seems not to have a breaking change, allow 1.4.x.
PR: 280621
Tested by: Админ всея АСУ-ВЭИ <admin@asu-vei.ru>
www/gitlab: fix regression from 09d7eada6c2c214adac9780307f2dd7689ab8660
Gitlab requires cssbundling 1.4.0.
As changelog of cssbundling seems not to have a breaking change, allow 1.4.x.
That patch is not approved from upstream and needs to be tested carefully.
PR: 280621
www/gitlab: Update RUN_DEPENDS
- Change RUN_DEPENDS from rubygem-octokit to rubygem-octokit8
- Change RUN_DEPENDS from rubygem-rexml to rubygem-rexml32
- Change RUN_DEPENDS from rubygem-rouge to rubygem-rouge42
- Bump PORTREVISION for dependency change
www/gitlab: fix regression from dbc3f874de613640cbc2151dcc4fa39ce6433461
bundler: failed to load command: puma (/usr/local/bin/puma)
/usr/local/www/gitlab/config/initializers/redis_client_patch.rb:8:in `<top
(required)>': New version of redis-client detected, please remove this file
(RuntimeError)
www/gitlab: fix database migration error
main: -- execute("ALTER TABLE \"ci_pipelines\" DROP CONSTRAINT
\"ci_pipelines_pkey\" \n")
main: == [advisory_lock_connection] object_id: 52240, pg_backend_pid: 3944
rake aborted!
StandardError: An error has occurred, all later migrations canceled:
(StandardError)
PG::DependentObjectsStillExist: ERROR: cannot drop constraint ci_pipelines_pkey
on table ci_pipelines because other objects depend on it
DETAIL: constraint fk_c262d728d4 on table p_ci_builds depends on index
ci_pipelines_pkey
HINT: Use DROP ... CASCADE to drop the dependent objects too.
https://gitlab.com/gitlab-org/gitlab/-/issues/462591#tophttps://gitlab.com/gitlab-org/gitlab/-/merge_requests/153560
www/gitlab: Update RUN_DEPENDS
- Change RUN_DEPENDS from rubygem-browser to rubygem-browser5
- Change RUN_DEPENDS from rubygem-grape-swagger to rubygem-grape-swagger20
- Change RUN_DEPENDS from rubygem-httparty to rubygem-httparty021
- Change RUN_DEPENDS from rubygem-semver_dialects to rubygem-semver_dialects2
- Bump PORTREVISION for dependency change
www/gitlab: add flavor support to also support the EE version
By default the port will build the CE edition.
If you use pkg, you will install it as usual with:
pkg install gitlab-ce
If you need the EE edition you can install it with:
pkg install gitlab-ee
Applied security upgrade to gitlab 10.7.5.
Fixed bug with wrong path for gitlab-workhouse that should fix artifacts
(reported by Felix <mail@felix.flornet.de>). This was fix upstream but is not
included in this version yet:
https://gitlab.com/gitlab-org/gitlab-ce/issues/46763
Update net/rubygem-grpc to 1.11.1 which is required for gitlab 10.7.5.
Sync dep net/rubygem-grpc with gitlab which uses now 1.11.1.
Added gitlab-pages again to dependencies as the new version builds again.
Reported by: Felix <mail@felix.flornet.de>
Reviewed by: swills (mentor)
Approved by: swills (mentor)
Differential Revision: https://reviews.freebsd.org/D15631
Update gitlab to 10.7.3.
For list of changes look here:
https://about.gitlab.com/2018/04/22/gitlab-10-7-released/
Please note that gitlab-pages is temporarily removed and will be added later if
upstream bug is fixed.
To not update to this version if you require gitlab-pages.
The Gemfile.lock is now generated on gitlab startup, so this should help with
Gemfile issues.
Reviewed by: swills (mentor)
Approved by: swills (mentor)
Differential Revision: https://reviews.freebsd.org/D15314
Changed the MAINTAINER of all my ports to have mfechner@FreeBSD.org listed.
Reviewed by: tz (mentor)
Approved by: tz (mentor)
Differential Revision: https://reviews.freebsd.org/D15270
