It would appear that chrome should be updated from 48.0.2564.{103_p1} ==> 48.0.2564.{109-1} The google-chrome fetch is failing: >>> Emerging (1 of 1) www-client/google-chrome-48.0.2564.103_p1::gentoo >>> Failed to emerge www-client/google-chrome-48.0.2564.103_p1, Log file: >>> '/var/tmp/portage/www-client/google-chrome-48.0.2564.103_p1/temp/build.log' >>> Jobs: 0 of 1 complete, 1 failed Load avg: 0.75, 0.83, 0.56 --2016-02-10 17:12:53-- https://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-stable_48.0.2564.103-1_amd64.deb Resolving dl.google.com... 216.58.216.142, 2607:f8b0:400a:806::200e Connecting to dl.google.com|216.58.216.142|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2016-02-10 17:12:53 ERROR 404: Not Found. !!! Couldn't download 'google-chrome-stable_48.0.2564.103-1_amd64.deb'. Aborting. * Fetch failed for 'www-client/google-chrome-48.0.2564.103_p1', Log file: * '/var/tmp/portage/www-client/google-chrome-48.0.2564.103_p1/temp/build.log' * Package: www-client/google-chrome-48.0.2564.103_p1 * Repository: gentoo * Maintainer: floppym@gentoo.org xmw@gentoo.org,chromium@gentoo.org * USE: abi_x86_64 amd64 elibc_glibc kernel_linux plugins userland_GNU * FEATURES: preserve-libs sandbox userpriv usersandbox * Please wait 24 hours and sync your tree before reporting a bug for google-chrome fetch failures. According to the browse-able mirror I look at (http://mirror.retrosnub.co.uk/apt/googlechrome/pool/main/g/google-chrome-stable/), it seems the latest versions are: google-chrome-stable_48.0.2564.109-1_amd64.deb 09-Feb-2016 18:40 48067952 google-chrome-stable_48.0.2564.109-1_i386.deb 09-Feb-2016 18:40 47625502 Reproducible: Always
Looks like this was done already in https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8d06997aacbd3b53642b41662271adae2c3766a4.
