[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: gitlab - install problems

(sorry replying this way, i wasn't subscribed to mailing list)

1) you are right, i didn't see that, it runs as user gitlab
4,5) new gitlab-shell in your repo fixes this issues, thanks

I have updated to your packages 8.3.0 and I had to run
bundle lock --update --local
in /usr/share/gitlab 

I have remembered more problems during install and reported them (on package 
 - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809559
 - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809560

-  user gitlab should be added to group redis, so it can access unix socket on 
disk (which must be enabled in redis package by hand - this could be mentioned 
in readme?)
- gitlab package missing dependency on ruby-state-machines-activerecord
- sometimes in future, can you soften dependency on postrgres to recommends? 
we use mysql to host gitlab db

With regards,

On Tuesday 29 of December 2015 23:12:53 Libor Klepáč wrote:
> Helo,
> first of all, I want to thank you for your hard work on packaging gitlab for
> Debian.
> I installed it from ~praveen repo to migrate from packages generated from
> packager.io
> I want to share some problems I encountered, i hope it don't come from this
> migration, because it's packaged a little differently.
> I had to upgrade system from Wheezy to Jessie and than to Stretch.
> 1) init script wants to run daemons under user "git" which (i believe) is
> not created by this package
> 2) init script doesn't work with systemd (some problem with policykit, when
> it tries to su to user git)
> 3) package doesn't migrate DB but creates new empty database in rake-tasks
> 4) package gitlab-shell doesn't contain /usr/share/gitlab-shell/hooks
> directory - maybe reason of
> https://gitlab.com/debian-ruby/TaskTracker/issues/40
> after copying this directory from source package, creation on repository
> started to work
> 5) weird paths created and expected by gitlab-shell
>  a) command paths in /usr/share/gitlab/.ssh/authorized_keys point to:
>  "/usr/lib/ruby/bin/gitlab-shell", i have had to create symlink
>    btw: authorized_keys should probably be somewhere in /var/lib, because
> it's generated ?
>  b) i have to generete more symlinks in /usr/lib/ruby to get gitlab-shell
> working
> ./bin/gitlab-shell -> /usr/share/gitlab-shell/bin/gitlab-shell
> ./config.yml -> /usr/share/gitlab-shell/config.yml
> ./gitlab-shell.log -> /usr/share/gitlab-shell/gitlab-shell.log
> ./.gitlab_shell_secret -> /usr/share/gitlab-shell/.gitlab_shell_secret
> ./lib/gitlab_init.rb -> /usr/lib/ruby/vendor_ruby/gitlab_init.rb
> ./lib/gitlab_keys.rb -> /usr/lib/ruby/vendor_ruby/gitlab_keys.rb
>  c) i some more symlinks in /usr/share/gitlab-shell
>   ./.gitlab_shell_secret -> /usr/share/gitlab/.gitlab_shell_secret
>  ./lib/gitlab_init.rb -> /usr/lib/ruby/vendor_ruby/gitlab_init.rb
>  ./lib/gitlab_shell.rb -> /usr/lib/ruby/vendor_ruby/gitlab_shell.rb
>  d) gitlab-shell logs to /usr/share/gitlab-shell/gitlab-shell.log
> Thanks for your work again,
> with regards,
> Libor

Reply to: