JakeHillion/nixpkgs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
aa5c7fb6f0
nixpkgs/pkgs/applications/version-management/gitlab/nulladapter.patch

34 lines
862 B
Diff
Raw Normal View History

gitlab: 8.5.12 -> 8.10.3, update module Fixes #14795.
2016-08-03 17:49:18 +01:00
diff --git a/Gemfile b/Gemfile
gitlab: 9.4.5 -> 9.5.2
2017-09-03 14:38:28 +01:00
index 4861171ef5..f6e701c548 100644
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way *all* Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598.
2016-01-30 13:47:04 +00:00
--- a/Gemfile
+++ b/Gemfile
gitlab: 9.4.5 -> 9.5.2
2017-09-03 14:38:28 +01:00
@@ -1,5 +1,7 @@
source 'https://rubygems.org'
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
+gem 'activerecord-nulldb-adapter'
gitlab: 9.4.5 -> 9.5.2
2017-09-03 14:38:28 +01:00
+
gem 'rails', '4.2.8'
gem 'rails-deprecated_sanitizer', '~> 1.0.3'
gitlab: 8.5.12 -> 8.10.3, update module Fixes #14795.
2016-08-03 17:49:18 +01:00
diff --git a/Gemfile.lock b/Gemfile.lock
gitlab: 9.4.5 -> 9.5.2
2017-09-03 14:38:28 +01:00
index 38944248f9..08ce4486ba 100644
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way *all* Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598.
2016-01-30 13:47:04 +00:00
--- a/Gemfile.lock
+++ b/Gemfile.lock
gitlab: 10.0.2 -> 10.1.1
2017-11-03 21:27:58 +00:00
@@ -33,6 +33,8 @@ GEM
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
activemodel (= 4.2.8)
activesupport (= 4.2.8)
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way *all* Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598.
2016-01-30 13:47:04 +00:00
arel (~> 6.0)
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
+ activerecord-nulldb-adapter (0.3.7)
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way *all* Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598.
2016-01-30 13:47:04 +00:00
+ activerecord (>= 2.0.0)
gitlab: 8.13.5 -> 8.15.4
2017-01-15 16:06:39 +00:00
activerecord_sane_schema_dumper (0.2)
rails (>= 4, < 5)
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
activesupport (4.2.8)
gitlab: 10.0.2 -> 10.1.1
2017-11-03 21:27:58 +00:00
@@ -963,6 +965,7 @@ PLATFORMS
gitlab: 8.5.12 -> 8.10.3, update module Fixes #14795.
2016-08-03 17:49:18 +01:00
DEPENDENCIES
RedCloth (~> 4.3.2)
gitlab: 8.10.6 -> 8.11.2
2016-08-26 13:08:53 +01:00
ace-rails-ap (~> 4.1.0)
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way *all* Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598.
2016-01-30 13:47:04 +00:00
+ activerecord-nulldb-adapter
gitlab: 8.13.5 -> 8.15.4
2017-01-15 16:06:39 +00:00
activerecord_sane_schema_dumper (= 0.2)
acts-as-taggable-on (~> 4.0)
gitlab: 10.0.2 -> 10.1.1
2017-11-03 21:27:58 +00:00
addressable (~> 2.5.2)
Reference in New Issue Copy Permalink