In a network where web proxy is necessary to access the internet www-plugins/chrome-binary-plugins always fail to download e.g.: >>> Emerging (2 of 8) www-plugins/chrome-binary-plugins-44.0.2403.39_beta1::gentoo >>> Downloading 'https://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-beta/google-chrome-beta_44.0.2403.39-1_amd64.deb' --2015-06-12 12:00:04-- https://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-beta/google-chrome-beta_44.0.2403.39-1_amd64.deb Resolving dl.google.com... 2a00:1450:4009:800::200e, 216.58.210.14 Connecting to dl.google.com|2a00:1450:4009:800::200e|:443... failed: Network is unreachable. Connecting to dl.google.com|216.58.210.14|:443... failed: Connection timed out. Retrying. --2015-06-12 12:01:05-- (try: 2) https://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-beta/google-chrome-beta_44.0.2403.39-1_amd64.deb Connecting to dl.google.com|2a00:1450:4009:800::200e|:443... failed: Network is unreachable. Connecting to dl.google.com|216.58.210.14|:443... failed: No route to host. !!! Couldn't download 'google-chrome-beta_44.0.2403.39-1_amd64.deb'. Aborting. This is not related to version of the package - I can copy-paste the URL into a browser and it downloads just fine. Please note I have http_proxy env variable set, and both sync and downloads of sources/binaries for other software works without a hitch, this problem is an exception to the rule, not a general issue with system setup. It appears that the download process simply ignores the environment settings in this case.
Sounds like a problem in wget or in portage. Please check whether the following command works from the terminal: wget 'https://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-beta/google-chrome-beta_44.0.2403.39-1_amd64.deb' Also, please explain your web proxy setup a bit, and attach output of "emerge --info wget gnutls openssl ca-certificates"
my guess is the proxy settings are bad. please post the exact settings and try running wget directly: wget https://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-beta/google-chrome-beta_44.0.2403.39-1_amd64.deb
You're right - http_proxy was set, but httpS_proxy was not... I wasn't aware there was second env variable for https, and I would expect to have failback to http_proxy if the other one wasn't set. Live and learn. Thank you for your help.
