On 2016, ഡിസംബർ 8 8:53:16 AM IST, Johannes Schauer <jo...@debian.org> wrote: >Hi, > >On Thu, 08 Dec 2016 04:12:57 +0100 Johannes Schauer <jo...@debian.org> >wrote: >> When I now enter my gitlab instance I only get a 502 error with the >message >> "Whoops, GitLab is taking too much time to respond". >> >> Since the last time I changed the version of a ruby package you told >me >> to run assets:precompile, I ran the following command: >> >> runuser -u gitlab -- sh -c 'cd /usr/share/gitlab && export $(cat >/etc/gitlab/gitlab-debian.conf) && rake assets:precompile >RAILS_ENV=production' >> Could not find grape-entity-0.5.1 in any of the sources >> Run `bundle install` to install missing gems. >> >> Given the error above, I suspect that the new ruby-grape-entity >version >> is the culprit here. > >in the hopes that the gitlab postinst maintainer script would contain >something >that fixes this problem, I ran "apt-get install --reinstall gitlab" >with the >following result: > >Verifying we have all required libraries... >Could not find gem 'grape-entity (~> 0.5.0)' in any of the gem sources >listed in >your Gemfile or available on this machine. >dpkg: error processing package gitlab (--configure): >subprocess installed post-installation script returned error exit >status 7 >Processing triggers for systemd (232-7) ... >Errors were encountered while processing: > gitlab >E: Sub-process /usr/bin/dpkg returned an error code (1)
This is fixed in git, you need to update ruby-grape-entity. > > >Thanks! > >cheers, josch