3
0
Fork 0
forked from mirrors/nixpkgs
nixpkgs/pkgs/applications/version-management/gitlab
talyz ed4a09c6f3 gitlab: Get rid of most 'already initialized constant'-warnings
On start, unicorn, sidekiq and other parts running ruby code emits
quite a few warnings similar to

/var/gitlab/state/config/application.rb:202: warning: already initialized constant Gitlab::Application::LOOSE_EE_APP_ASSETS
/nix/store/ysb0lgbzxp7a9y4yl8d4f9wrrzy9kafc-gitlab-ee-12.3.5/share/gitlab/config/application.rb:202: warning: previous definition of LOOSE_EE_APP_ASSETS was here
/var/gitlab/state/lib/gitlab.rb:38: warning: already initialized constant Gitlab::COM_URL
/nix/store/ysb0lgbzxp7a9y4yl8d4f9wrrzy9kafc-gitlab-ee-12.3.5/share/gitlab/lib/gitlab.rb:38: warning: previous definition of COM_URL was here

This seems to be caused by the same ruby files being evaluated
multiple times due to the paths being different - sometimes they're
loaded using the direct path and sometimes through a symlink, due to
our split between config and package data. To fix this, we make sure
that the offending files in the state directory always reference the
store path, regardless of that being the real file or a symlink.
2019-10-19 19:30:28 +02:00
..
gitaly Merge pull request #70216 from talyz/gitlab_12_3_2 2019-10-09 00:27:04 +02:00
gitlab-shell gitlab: Add myself to list of maintainers 2019-10-08 16:37:01 +02:00
gitlab-workhorse gitlab: Add myself to list of maintainers 2019-10-08 16:37:01 +02:00
rubyEnv gitlab: Refactor for new repo structure 2019-10-08 15:52:11 +02:00
data.json gitlab: 12.3.4 -> 12.3.5 2019-10-08 16:35:50 +02:00
default.nix gitlab: Get rid of most 'already initialized constant'-warnings 2019-10-19 19:30:28 +02:00
fix-grpc-ar.patch gitlab: 11.10.8 -> 12.0.3 2019-07-14 23:03:39 +02:00
remove-hardcoded-locations.patch
reset_token.rake
update.py gitlab: Refactor for new repo structure 2019-10-08 15:52:11 +02:00
yarnPkgs.nix gitlab: Build frontend assets from source 2019-10-08 11:24:06 +02:00