emerge -vp gcc These are the packages that would be merged, in order: Calculating dependencies A * Digest verification failed: * /usr/portage/sys-devel/gcc/gcc-4.8.4.ebuild * Reason: Failed on SHA256 verification * Got: e9f81a015fe84b6d9960d12e2ff9e50fc181fe28a5abe1ead3079c4af8bdd782 * Expected: 482475868425d5512fa4749866533d87dd7c9a4f1309c19f44bb0a63b4c8ae1a h * Digest verification failed: * /usr/portage/sys-devel/gcc/gcc-5.1.0.ebuild * Reason: Failed on SHA256 verification * Got: 54f2d20db4df60a9e309a1c48c9758d930ff8dc73bc4afe638fdd47c576a973c * Expected: f982e8c7efabdd87369bcc90794ba6bc4656d86982d706c07ba0bb615f2f9358 * Digest verification failed: * /usr/portage/sys-devel/gcc/gcc-4.9.2.ebuild * Reason: Failed on SHA256 verification * Got: 4edc583271183a97bff80d87d7dbb5e2913d386d638b2174718040c50c8f2579 * Expected: 44366dacce342cca6ae1875e0ca3c00db1dfd2b97b3310b85c2c4ce79b31baae ... done!
Same problem here, manifest is broken by the last commit.
not a whole lot we can do currently. my guess is the rsync ran in the window my repoman commit and sent out the ebuilds while the manifest was regenerated. you can clearly see that 2 hours ago the Manifest was updated with the hashes you're reporting: https://sources.gentoo.org/sys-devel/gcc/Manifest?r1=1.1624&r2=1.1625
gcc-5.1.0 changed was committed: Wed May 27 16:01:17 2015 UTC by vapier manifest was committed: Wed May 27 16:01:22 2015 UTC by vapier so we were just unlucky that the rsync process ran in that 5 second window
Yup, with tree from >=Wed, 27 May 2015 17:45:01 +0000 the error is gone.
