Your message dated Fri, 08 Apr 2022 11:21:46 +0530 with message-id <[email protected]> and subject line Re: Bug#1008932: gitlab-sidekiq cannot find graphiql-rails has caused the Debian Bug report #1008932, regarding gitlab-sidekiq cannot find graphiql-rails to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 1008932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008932 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: gitlab Version: 14.7.7+ds1-2~fto11+2 Severity: normal Dear Maintainer, Recently, I tried to upgrade Gitlab to 14.7.7+ds1-2~fto11+2. Unfortunately, gitlab-sidekiq does not start afterwards but fails as it cannot find graphiql-rails: gitlab-sidekiq[8334]: Could not find gem 'graphiql-rails (~> 1.8)' in any of the gem sources listed in your Gemfile However, in /var/lib/gitlab/.gem/gems (I fixed the owner as described in the wiki), the gem is present (in directory graphiql-rails-1.8.0). Unfortunately, I cannot uninstall the apt package ruby-graphiql-rails (version 1.4.10-1) as gitlab still depends on it. So, I assumed that Gitlab finds the graphiql-rails package installed by apt. After I had updated the Gemfile to require version 1.4 of graphiql-rails, I can indeed successfully start gitlab-sidekiq. With this, Gitlab starts again, however some features do not work. Most notably, I cannot merge a morge request anymore. Thanks for your support! Best, Maximilian
--- End Message ---
--- Begin Message ---2022, ഏപ്രിൽ 7 9:15:31 PM IST, Maximilian Stein <[email protected]>ൽ എഴുതി > >> So I will wait if anyone else can confirm or reproduce this issue >> before adding GEM_PATH. Did you have GEM_HOME set in >> /etc/gitlab/gitlab-debian.conf ? > >No, actually not. I now tested with > > GEM_HOME=/var/lib/gitlab/.gem > >and I can confirm that this alone suffices. So, setting GEM_PATH is not >needed when GEM_HOME is set correctly. Thanks for confirmation. Closing this bug. >Best, >Maximilian > -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
--- End Message ---
_______________________________________________ Pkg-ruby-extras-maintainers mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
