Few days after one problem is solved with portage snapshots another one appeared. Fetching most recent snapshot ... Trying to retrieve 20160201 snapshot from http://mirror.yandex.ru/gentoo-distfiles ... Fetching file portage-20160201.tar.xz.md5sum ... Fetching file portage-20160201.tar.xz.gpgsig ... Fetching file portage-20160201.tar.xz ... Checking digest ... Checking signature ... gpg: Signature made Tue 02 Feb 2016 01:49:45 AM CET using RSA key ID C9189250 gpg: Good signature from "Gentoo Portage Snapshot Signing Key (Automated Signing Key)" [ultimate] Getting snapshot timestamp ... Syncing local tree ... emerge-webrsync: error: tar failed to extract the image. tarball is corrupt? (/var/tmp/portage/webrsync-RXxnqv/portage-20160201.tar.xz) * Latest snapshot date: 20160131 * * Approximate snapshot timestamp: 1454287500 * Current local timestamp: 1454286901 * * The current local timestamp is possibly identical to the * timestamp of the latest snapshot. In order to force sync, use * the --revert option or remove the timestamp file located at * '/usr/portage/metadata/timestamp.x'. Didn't fail digest check or gpg signature check. Not sure what the problem is. Reproducible: Always
Same problem as bug 573642
*** This bug has been marked as a duplicate of bug 573642 ***
