Re: [Gitlab] Current Status of the port

2015-08-10 Thread Torsten Zuehlsdorff
Hello, I will have a look at it. Is there anything in Admin Area - Logs which could be helpful? No, it looks to be a javascript issue, clicking the button doesn't even trigger any sort of http request, it just does nothing. I think I may have figured out the issue. jquery 4.x isn't

Re: [Gitlab] Current Status of the port

2015-08-06 Thread Steve Wills
On Thu, Aug 06, 2015 at 04:52:34PM +0200, Torsten Zuehlsdorff wrote: On 05.08.2015 19:10, Steve Wills wrote: I will have a look at it. Is there anything in Admin Area - Logs which could be helpful? No, it looks to be a javascript issue, clicking the button doesn't even trigger any

Re: [Gitlab] Current Status of the port

2015-08-06 Thread Torsten Zuehlsdorff
On 05.08.2015 19:10, Steve Wills wrote: I will have a look at it. Is there anything in Admin Area - Logs which could be helpful? No, it looks to be a javascript issue, clicking the button doesn't even trigger any sort of http request, it just does nothing. I think I may have figured out the

Re: [Gitlab] Current Status of the port

2015-08-06 Thread Torsten Zuehlsdorff
On 06.08.2015 17:16, Steve Wills wrote: I will have a look at it. Is there anything in Admin Area - Logs which could be helpful? No, it looks to be a javascript issue, clicking the button doesn't even trigger any sort of http request, it just does nothing. I think I may have figured out the

Re: [Gitlab] Current Status of the port

2015-08-06 Thread Torsten Zuehlsdorff
On 06.08.2015 17:52, Steve Wills wrote: I will have a look at it. Is there anything in Admin Area - Logs which could be helpful? No, it looks to be a javascript issue, clicking the button doesn't even trigger any sort of http request, it just does nothing. I think I may have figured out the

Re: [Gitlab] Current Status of the port

2015-08-06 Thread Steve Wills
On Thu, Aug 06, 2015 at 05:28:45PM +0200, Torsten Zuehlsdorff wrote: On 06.08.2015 17:16, Steve Wills wrote: I will have a look at it. Is there anything in Admin Area - Logs which could be helpful? No, it looks to be a javascript issue, clicking the button doesn't even trigger any

Re: [Gitlab] Current Status of the port

2015-08-05 Thread Torsten Zuehlsdorff
Hello, I will see tomorrow, if i can make portlint happier :) Greet news! Can i help you in any way? There is an update to GitLab: https://about.gitlab.com/2015/08/04/gitlab-7-dot-13-dot-3-released/ if you want to see about updating that'd be cool. Done. Also, I noticed that after

Re: [Gitlab] Current Status of the port

2015-08-05 Thread Steve Wills
On Wed, Aug 05, 2015 at 05:02:15PM +0200, Torsten Zuehlsdorff wrote: Done. Thanks, I'll give it a go. I will have a look at it. Is there anything in Admin Area - Logs which could be helpful? No, it looks to be a javascript issue, clicking the button doesn't even trigger any sort of http

Re: [Gitlab] Current Status of the port

2015-08-05 Thread Steve Wills
On Wed, Aug 05, 2015 at 03:21:05PM +, Steve Wills wrote: On Wed, Aug 05, 2015 at 05:02:15PM +0200, Torsten Zuehlsdorff wrote: Done. Thanks, I'll give it a go. I will have a look at it. Is there anything in Admin Area - Logs which could be helpful? No, it looks to be a

Re: [Gitlab] Current Status of the port

2015-08-05 Thread Steve Wills
On Wed, Aug 04, 2015 at 04:35:12PM +, Steve Wills wrote: On Wed, Aug 05, 2015 at 03:21:05PM +, Steve Wills wrote: On Wed, Aug 05, 2015 at 05:02:15PM +0200, Torsten Zuehlsdorff wrote: Done. Thanks, I'll give it a go. I will have a look at it. Is there anything in Admin

Re: [Gitlab] Current Status of the port

2015-08-04 Thread Torsten Zuehlsdorff
On 03.08.2015 23:58, Steve Wills wrote: Okay. I removed the mysql option. But its just a revert to get it back, if you want. I also reworked all the slave-ports and created a new patch. After unpacking the attached .shar file apply the contained patch gitlab.diff to /usr/ports. Than get the

Re: [Gitlab] Current Status of the port

2015-08-03 Thread Torsten Zuehlsdorff
Hello, You need explicitly enabling it in config/gitlab.yml. Gitlab needs the Gem installed, but for further use you need explicit configuration. Its commented out by default. So it's required to run but not enabled by default? Sounds like it should go into RUN_DEPENDS then. No they are

Re: [Gitlab] Current Status of the port

2015-08-03 Thread Steve Wills
On Mon, Aug 03, 2015 at 10:29:15AM +0200, Torsten Zuehlsdorff wrote: Hello, # cd /usr/ports/devel/rubygem-gitlab_git-rails41 # portlint -AC FATAL: Makefile: the last line of a slave port's Makefile has to be .include ${MASTERDIR}/Makefile FATAL: Makefile: extra item MASTERDIR placed

Re: [Gitlab] Current Status of the port

2015-08-03 Thread Torsten Zuehlsdorff
Hello, I've created a basic working configuration for default. You just should change the host in config/gitlab.yml, if you want to use something other than localhost. The rest should work. But please test carefully, i've done many changes in the last months. I built the packages and

Re: [Gitlab] Current Status of the port

2015-08-01 Thread Steve Wills
Hi again, On 08/01/2015 10:51, Steve Wills wrote: Hi, On 07/31/2015 10:49, Torsten Zuehlsdorff wrote: To setup GitLab follow the quide: https://github.com/t-zuehlsdorff/gitlabhq/blob/master/doc/install/installation-freebsd.md I've created a basic working configuration for default. You

Re: [Gitlab] Current Status of the port

2015-08-01 Thread Steve Wills
Hi, On 07/31/2015 10:49, Torsten Zuehlsdorff wrote: To setup GitLab follow the quide: https://github.com/t-zuehlsdorff/gitlabhq/blob/master/doc/install/installation-freebsd.md I've created a basic working configuration for default. You just should change the host in config/gitlab.yml, if

Re: [Gitlab] Current Status of the port

2015-07-31 Thread Torsten Zuehlsdorff
Hello Steve, As mentioned you will needed 40 currently uncommited ports. Today i have not enough time to create a patch for you. But i try to get this done tomorrow! After grabbing the shars that are in bugzilla at the moment, it seems these ports are still missing: [..] list of missing

Re: [Gitlab] Current Status of the port

2015-07-31 Thread Torsten Zuehlsdorff
Hello, You was a little bit faster than me. Today i compiled a number of changes needed to get GitLab build. I've found some minor problems and fixed them too. You need 3 steps to get the ports-tree in the correct shape: 1. apply the attachment gitlab-portstree-patch.diff to /usr/ports/ 2.

Re: [Gitlab] Current Status of the port

2015-07-31 Thread Steve Wills
On Thu, Jul 30, 2015 at 05:39:30PM +0200, Torsten Zuehlsdorff wrote: As mentioned you will needed 40 currently uncommited ports. Today i have not enough time to create a patch for you. But i try to get this done tomorrow! After grabbing the shars that are in bugzilla at the moment, it seems

Re: [Gitlab] Current Status of the port

2015-07-31 Thread Steve Wills
Hi, On Fri, Jul 31, 2015 at 04:49:59PM +0200, Torsten Zuehlsdorff wrote: 3. get the most actual GitLab copy from svn://svn.toco-domains.de/freebsd-ports/www/gitlab Seems identical to the one in the shar, as far as I can tell. Fine. It shouldn't be in the shar, but its okay ;) Eh,

[Gitlab] Current Status of the port

2015-07-30 Thread Torsten Zuehlsdorff
Hello all, after porting GitLab to support Rails 4.2 was not very successful, i've started to get Rails 4.1 back into ports. You've already seen the PRs ;) Normally i do not talk much if i'm not confident in the things i'm saying. But today i reached a point, where i would say, that only

Re: [Gitlab] Current Status of the port

2015-07-30 Thread Steve Wills
Hi, Torsten, On Thu, Jul 30, 2015 at 04:57:25PM +0200, Torsten Zuehlsdorff wrote: Hello all, after porting GitLab to support Rails 4.2 was not very successful, i've started to get Rails 4.1 back into ports. You've already seen the PRs ;) Normally i do not talk much if i'm not confident