Created attachment 569296 [details] build log * Running bundle install --deployment --without development test thin postgres ... Don't run Bundler as root. Bundler can ask for sudo if it is needed, and installing your bundle as root will break this application for all non-root users on this machine. Fetching source index from https://rubygems.org/ Retrying fetcher due to error (2/4): Bundler::HTTPError Could not fetch specs from https://rubygems.org/ Retrying fetcher due to error (3/4): Bundler::HTTPError Could not fetch specs from https://rubygems.org/ Retrying fetcher due to error (4/4): Bundler::HTTPError Could not fetch specs from https://rubygems.org/ Could not fetch specs from https://rubygems.org/ * ERROR: www-apps/gitlabhq-11.8.2::gitlab failed (install phase): * bundler failed
I just tried to reproduce the error and the ebuild was installed properly. This seems to be a connection problem on your side, since bundler could not connect to https://rubygems.org. Please make sure that you can properly connect to https://rubygems.org. Also check proxy settings if you are using a proxy. I will close this issue. Feel free to re-open if the error remains.
The error is happening in install phase and I already tested the connection to rubygems.org and bundler. I'm using ruby24. Could this be a limitation from any gem missing in ruby24? Did you test the installation with ruby24? And during install phase is the following message expected to appear? * Running bundle install --deployment --without development test thin postgres ... Don't run Bundler as root. Bundler can ask for sudo if it is needed, and installing your bundle as root will break this application for all non-root users on this machine. Thanks
I forget to mention that I could install successfully gitlabhq 11.8.1.
I can confirm that bundler has a problem downloading https://rubygems.org/specs.4.8.gz: Retrying fetcher due to error (4/4): Bundler::HTTPError Could not fetch specs from https://rubygems.org/ Gem::RemoteFetcher::FetchError: Errno::ENETUNREACH: Failed to open TCP connection to rubygems.org:443 (Network is unreachable - connect(2) for "rubygems.org" port 443) (https://rubygems.org/specs.4.8.gz) /usr/lib64/ruby/site_ruby/2.4.0/rubygems/remote_fetcher.rb:311:in `rescue in fetch_path' /usr/lib64/ruby/site_ruby/2.4.0/rubygems/remote_fetcher.rb:283:in `fetch_path' This only occurs when Portage is running "bundle install" during an emerge. When I manually run "bundle install" or try to fetch the specs i.e. via wget, things work fine.
Running tcpdump during emerge shows me that portage does not even try to reach "rubygems.org": No single TCP package is sent to one of the rubygems.org hosts.
We assume a problem when running "bundle install" from within the portage sandbox but we need to further investigate this issue.
We can confirm that the network-sandbox feature of portage is responsible for this. A temporary workaround is to disable the network-sandbox while emerging the ebuild: FEATURES="-network-sandbox" emerge -av1 gitlabhq
Issue should be fixed with the latest commit: https://gitlab.awesome-it.de/overlays/gitlab/commit/c6c996bb837b6f47203abbc0c8c0b7b4ab2b3e73. Feel free to-reopen if the issue still exists.
