I'm trying to update www/gitlab from 8.16 to 8.17. I'm building from ports tree. The revision used is 441153. After build and install all packages gitlab is showing this message when I try start: [root@mintaka /usr/ports/www/gitlab]# /usr/local/etc/rc.d/gitlab start Starting GitLab Unicorn Starting GitLab Sidekiq Could not find mime-types-2.99.3 in any of the sources Run `bundle install` to install missing gems. The gitlab-workhorse is already running with pid 0, not restarting The most curious is that from the ports tree there is not exist a port version of mime-types-2.99.3. r416246 | pi | 2016-06-01 12:28:42 -0300 (Wed, 01 Jun 2016) | 16 lines misc/rubygem-mime-types: 2.99.1 -> 3.1 - Version 3.0 is a major release that requires Ruby 2.0 compatibility and removes deprecated functions. - The columnar registry format introduced in 2.6 has been made the primary format - the registry data has been extracted from this library and put into ruby-mime-types-data - Additionally, mime-types is now licensed exclusively under the MIT licence and there is a code of conduct in effect. - There are a number of other smaller changes described in https://github.com/mime-types/ruby-mime-types/blob/master/History.rdoc PR: 209936 Submitted by: Torsten Zuehlsdorff <ports@toco-domains.de> ------------------------------------------------------------------------ So, the mime-types is going from 2.99.1 to 3.1. Why my gitlab installation is requiring mime-types 2.99.3?
This is a little odd, since GitLab 8.17 just runs fine with mime-types 3.1. Did you remove /usr/local/www/gitlab/Gemfile.lock before the restart? This is the most common source for this type of issues. If you didn't removed it first, GitLab will look for old Gemfiles, because the were persisted there. After deleting the file it will look for installed gems. So, please try this.
Hi Torsten Zuehlsdorff You are right! I do not know how to say because I was sure I removed this file but it really was there. I removed the file and the upgrade proceeded. This update was particularly difficult because before, step 5 ran as root and not with a sudo git. In any case I did it. The only issue is that in the recent versions of recaptcha a change from public_key to site_key and private_key to secret_key was necessary like reported here: https://stackoverflow.com/questions/40916905/rails-server-crashes-due-to-captcha after it gitlab works with visible problems. In any case, thank you very much by your help.
(In reply to otacilio.neto from comment #2) sorry. gitlab works WITHOUT visible problems.