Mick wrote: > This is the second machine I am getting a 404 in as many weeks with this > package. Is it a known problem, or am I the only one suffering from this? > > >>>> Emerging (1 of 8) www-plugins/chrome-binary- > plugins-41.0.2272.76_p1::gentoo > * Fetching files in the background. To view fetch progress, run > * `tail -f /var/log/emerge-fetch.log` in another terminal. >>>> Downloading 'https://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-stable_41.0.2272.76-1_amd64.deb' > --2015-03-10 22:02:09-- > https://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-stable_41.0.2272.76-1_amd64.deb > Resolving dl.google.com... 216.58.210.46, 2a00:1450:4009:800::200e > Connecting to dl.google.com|216.58.210.46|:443... connected. > HTTP request sent, awaiting response... 404 Not Found > 2015-03-10 22:02:09 ERROR 404: Not Found. > > !!! Couldn't download 'google-chrome-stable_41.0.2272.76-1_amd64.deb'. > Aborting. > * Fetch failed for 'www-plugins/chrome-binary-plugins-41.0.2272.76_p1', Log > file: > * '/var/tmp/portage/www-plugins/chrome-binary- > plugins-41.0.2272.76_p1/temp/build.log' > * Please wait 24 hours and sync your portage tree before reporting fetch > failures. >
I don't use the package but tried to fetch it to test. Same failure here too. Can you force it to use a different mirror or is it google's and that's it? Dale :-) :-)