Re: migrating to Debian gitlab

2016-04-14 Thread Olivier Berger
Pirate Praveen writes: > >>Beyond that I couldn't test, my VM only has 1 GiB of RAM and no >>swap, and that is apparently not sufficient for gitlab (unicorn >>complains that it's out of memory). Which seems weird to me, >>because this was otherwise an empty throwaway VM; an empty >>instance using

Re: migrating to Debian gitlab

2016-04-03 Thread Pirate Praveen
Gitlab Inc (gitlab.com) funded 60 days of work on debian packaging and here is the summary. Detailed work log is available at https://poddery.com/tags/debian-gitlab-months Now I'll start working on gitlab.debian.net and keep the package updated. 20 more days of funding is left. - Work started on

Re: migrating to Debian gitlab

2016-03-23 Thread Pirate Praveen
[adding backports to cc] On Sunday 21 February 2016 05:01 PM, Pirate Praveen wrote: > I have started backporting gitlab for jessie #815216 has status updates. I have built it on jessie (with tests disabled for some packages). http://mahishasura.pxq.in/ has the gitlab package for jessie. I have a

Re: migrating to Debian gitlab

2016-02-21 Thread Pirate Praveen
On Sunday 21 February 2016 06:52 PM, Johannes Schauer wrote: >> There is an issue with sidekiq pid in the logs, but service is fine. Can >> some one help here? > > is this reported as a bug? That would help to collect information about the > problem. I have created #815432 to track this issue. >

Re: migrating to Debian gitlab

2016-02-21 Thread Johannes Schauer
Hi, Quoting Pirate Praveen (2016-02-21 12:31:25) > On Monday 15 February 2016 11:35 PM, Pirate Praveen wrote: > >> systemd does not create any pid files. It only reads them to > >> figure out which PID of a multi-process Type=forking service is > >> the main PID of that service. > > > > Thanks fo

Re: migrating to Debian gitlab

2016-02-21 Thread Pirate Praveen
On Monday 15 February 2016 11:35 PM, Pirate Praveen wrote: >> systemd does not create any pid files. It only reads them to >> figure out which PID of a multi-process Type=forking service is >> the main PID of that service. > > Thanks for the clarification. There is an issue with sidekiq pid in th

Re: migrating to Debian gitlab

2016-02-15 Thread Paul Wise
On Tue, Feb 16, 2016 at 2:56 AM, Pirate Praveen wrote: > Also I remember reading about someone willing to offer machines for debian > work. Is it GPLHost? There are several options available: https://wiki.debian.org/ServicesHosting -- bye, pabs https://wiki.debian.org/PaulWise

Re: migrating to Debian gitlab

2016-02-15 Thread Pirate Praveen
On 2016, ഫെബ്രുവരി 15 10:05:08 PM IST, Christian Seiler wrote: >On 02/15/2016 04:56 PM, Pirate Praveen wrote: >> I have to verify if pid file ownership is causing problems. If >> systemd created pidfile as root and unicorn is writing to it as >> gitlab user, it will fail. I'll check this now. >

Re: migrating to Debian gitlab

2016-02-15 Thread Christian Seiler
On 02/15/2016 04:56 PM, Pirate Praveen wrote: > I have to verify if pid file ownership is causing problems. If > systemd created pidfile as root and unicorn is writing to it as > gitlab user, it will fail. I'll check this now. systemd does not create any pid files. It only reads them to figure out

Re: migrating to Debian gitlab

2016-02-15 Thread Pirate Praveen
On 2016, ഫെബ്രുവരി 15 9:00:26 PM IST, Christian Seiler wrote: >On 02/15/2016 03:42 PM, Pirate Praveen wrote: >> While trying to move files that are created at runtime to /var, I >> realized /var/run/gitlab won't persist across reboots. > >Well, thats kind of the semantics it was designed for: /

Re: migrating to Debian gitlab

2016-02-15 Thread Johannes Schauer
Hi, Quoting Christian Seiler (2016-02-15 16:30:26) > - the other services that use ExecStart=/bin/sh bin/$NAME start >and ExecStop=/bin/sh bin/$NAME stop are problematic, because >in the systemd service file you declare PIDFile to be in >/run/gitlab, while the configuration that's rea

Re: migrating to Debian gitlab

2016-02-15 Thread Christian Seiler
On 02/15/2016 03:42 PM, Pirate Praveen wrote: > While trying to move files that are created at runtime to /var, I > realized /var/run/gitlab won't persist across reboots. Well, thats kind of the semantics it was designed for: /run (formerly /var/run, which is now a symlink to /run) is not supposed

Re: migrating to Debian gitlab (was: Re: GitLab B.V. to host free-software GitLab for Debian project)

2016-02-15 Thread Johannes Schauer
Hi, Quoting Marco d'Itri (2016-02-15 16:05:20) > On Feb 15, Pirate Praveen wrote: > > More systemd troubles. > > > > While trying to move files that are created at runtime to /var, > > I realized /var/run/gitlab won't persist across reboots. I have added > This is not related to systemd, BTW.

Re: migrating to Debian gitlab (was: Re: GitLab B.V. to host free-software GitLab for Debian project)

2016-02-15 Thread Marco d'Itri
On Feb 15, Pirate Praveen wrote: > More systemd troubles. > > While trying to move files that are created at runtime to /var, > I realized /var/run/gitlab won't persist across reboots. I have added This is not related to systemd, BTW. -- ciao, Marco signature.asc Description: PGP signature

Re: migrating to Debian gitlab (was: Re: GitLab B.V. to host free-software GitLab for Debian project)

2016-02-15 Thread Pirate Praveen
More systemd troubles. While trying to move files that are created at runtime to /var, I realized /var/run/gitlab won't persist across reboots. I have added a RuntimeDirectory=gitlab option to gitlab service files, but gitlab-unicorn can't stay alive. It starts and writes /run/gitlab/unicorn.pi

Re: migrating to Debian gitlab (was: Re: GitLab B.V. to host free-software GitLab for Debian project)

2016-02-12 Thread Dimitri John Ledkov
On 12 Feb 2016 4:59 a.m., "Holger Levsen" wrote: > > On Freitag, 12. Februar 2016, Dimitri John Ledkov wrote: > > [ -d /run/systems/system ] specifically, as per sd_booted upstream API. > > typo, you ment [ -d /run/systemd/system ] > I hate predictive text on my phone. It has no systemd in the di

Re: migrating to Debian gitlab (was: Re: GitLab B.V. to host free-software GitLab for Debian project)

2016-02-12 Thread Holger Levsen
On Freitag, 12. Februar 2016, Dimitri John Ledkov wrote: > [ -d /run/systems/system ] specifically, as per sd_booted upstream API. typo, you ment [ -d /run/systemd/system ] :) signature.asc Description: This is a digitally signed message part.

Re: migrating to Debian gitlab (was: Re: GitLab B.V. to host free-software GitLab for Debian project)

2016-02-12 Thread Dimitri John Ledkov
On 11 Feb 2016 3:37 p.m., "Adam Borowski" wrote: > > On Thu, Feb 11, 2016 at 11:59:09PM +0530, Pirate Praveen wrote: > > Checking /proc/cmdline was working in my test machine as I had systemd before it became the default. > > > > I think checking /proc/1/cmdline will be a better method of checking

Re: migrating to Debian gitlab

2016-02-11 Thread Pirate Praveen
On Friday 12 February 2016 02:06 AM, Adam Borowski wrote: > On Thu, Feb 11, 2016 at 11:59:09PM +0530, Pirate Praveen wrote: >> Checking /proc/cmdline was working in my test machine as I had systemd >> before it became the default. >> >> I think checking /proc/1/cmdline will be a better method of c

Re: migrating to Debian gitlab

2016-02-11 Thread Christian Seiler
On 02/11/2016 09:36 PM, Adam Borowski wrote: > On Thu, Feb 11, 2016 at 11:59:09PM +0530, Pirate Praveen wrote: >> Checking /proc/cmdline was working in my test machine as I had systemd >> before it became the default. >> >> I think checking /proc/1/cmdline will be a better method of checking syste

Re: migrating to Debian gitlab (was: Re: GitLab B.V. to host free-software GitLab for Debian project)

2016-02-11 Thread Adam Borowski
On Thu, Feb 11, 2016 at 11:59:09PM +0530, Pirate Praveen wrote: > Checking /proc/cmdline was working in my test machine as I had systemd before > it became the default. > > I think checking /proc/1/cmdline will be a better method of checking systemd. /proc/1/cmdline will be wrong in chroots if t

Re: migrating to Debian gitlab (was: Re: GitLab B.V. to host free-software GitLab for Debian project)

2016-02-11 Thread Pirate Praveen
On 2016, ഫെബ്രുവരി 11 11:18:14 PM IST, Johannes Schauer wrote: >Hi, > >Quoting Pirate Praveen (2016-02-11 16:58:56) >> You can use, >> >> systemctl start gitlab.target >> >> as init script has problems with systemd. The installation is >complete otherwise. >> >> I added systemd unit files a

Re: migrating to Debian gitlab (was: Re: GitLab B.V. to host free-software GitLab for Debian project)

2016-02-11 Thread Johannes Schauer
Hi, Quoting Pirate Praveen (2016-02-11 16:58:56) > You can use, > > systemctl start gitlab.target > > as init script has problems with systemd. The installation is complete > otherwise. > > I added systemd unit files already and I will add a check for systemd to fix > the bug. thanks, that

Re: migrating to Debian gitlab (was: Re: GitLab B.V. to host free-software GitLab for Debian project)

2016-02-11 Thread Pirate Praveen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2016, ഫെബ്രുവരി 11 8:44:45 PM IST, Johannes Schauer wrote: >Hi, > >Quoting IOhannes m zmölnig (Debian/GNU) (2016-02-11 13:17:36) >> thank you very much for all your efforts! > >let me express my gratitude as well! > >Thank you for all your hard

migrating to Debian gitlab (was: Re: GitLab B.V. to host free-software GitLab for Debian project)

2016-02-11 Thread Johannes Schauer
Hi, Quoting IOhannes m zmölnig (Debian/GNU) (2016-02-11 13:17:36) > thank you very much for all your efforts! let me express my gratitude as well! Thank you for all your hard work! It seems installing gitlab pulled in more than 330 (!!) ruby packages. > now i only need a migration plan :-) If