[Gitlab] Current status (and problem ;)) of the new port
    Torsten Zuehlsdorff 
    info at toco-domains.de
       
    Fri Jul  3 08:10:42 UTC 2015
    
    
  
Hello all,
the work at the gitlab-port is slow but steadily. :)
The current version of my work can be found here with anonymous access:
svn://svn.toco-domains.de/freebsd-ports/www/gitlab
Currently all dependencies are defined and also in the needed version in 
the ports-tree. :)
Attention: when trying to install the port, there will be at least 274 
rubygems needed/installed ;)
Basis commands like make install, make reinstall, make deinstall, make 
stage-qa already works.
Also all defined options (except Kerberos-support) are working. The 
needed change of the Gemfile when selecting an option is already done.
At the moment i stuck at the point, when trying to create the database 
tables for gitlab. After an:
# cd /usr/local/www/gitlab && rake gitlab:setup
I get this error message:
=== Start ===
Bundler could not find compatible versions for gem "rack":
   In Gemfile:
     rack (>= 1.1) ruby
     gitlab-grack (>= 2.0.0.rc2) ruby depends on
       rack (~> 1.5.1) ruby
     rack (>= 0) ruby
     rack (~> 1.4) ruby
     rack (~> 1.0) ruby
     rack (>= 1.0) ruby
     rack (>= 1.3.0) ruby
     rack (>= 0) ruby
     rack (>= 0.4) ruby
     rack (>= 0) ruby
     rack (>= 1.0.0) ruby
     rack (~> 1.5) ruby
     html-pipeline-gitlab (>= 0.1) ruby depends on
       actionpack (~> 4) ruby depends on
         rack (~> 1.6) ruby
     rack (>= 1.0) ruby
     rack (~> 1.0) ruby
=== End ===
While fixing an similar error message for rubygem-twitter-stream i have 
problems to even understand from which gem this error comes from. Or why 
it comes. The following rack-versions are already installed:
# pkg info | grep rubygem-rack
rubygem-rack-1.4.7,3           Rack, a Ruby Webserver Interface
rubygem-rack15-1.5.5,4         Rack, a Ruby Webserver Interface
rubygem-rack16-1.6.4           Rack, a Ruby Webserver Interface
Has somebody an idea from which port the message comes or what needs to 
be patched to get around this?
Thanks and greetings,
Torsten
    
    
More information about the freebsd-ruby
mailing list