>>> Verifying ebuild manifests !!! Digest verification failed: !!! /usr/portage/dev-util/xxdi/metadata.xml !!! Reason: Failed on SHA256 verification !!! Got: 4584cfc74776dcb4d6976a3686a249537cb81b1f037d95bece3b0f63dba016dc !!! Expected: 503c83eefd31a7c19429e12befc0a41c5e773557e35a10cfce23a618e68e6392 >>> Emerging (1 of 1) dev-util/xxdi-1.0.0::gentoo !!! Digest verification failed: !!! /usr/portage/dev-util/xxdi/metadata.xml !!! Reason: Failed on SHA256 verification !!! Got: 4584cfc74776dcb4d6976a3686a249537cb81b1f037d95bece3b0f63dba016dc !!! Expected: 503c83eefd31a7c19429e12befc0a41c5e773557e35a10cfce23a618e68e6392 >>> Failed to emerge dev-util/xxdi-1.0.0 Reproducible: Always Steps to Reproduce: 1. xxdi is emerged as a dependency.. and fails. 2. 3. it does so for a week already Expected Results: building stuff. I was under the impression such basic info would be verified before publishing... This kind of mishaps should not happen, imho it should be a blocker as some basic consistency is failing..
Please sync your tree and try again. If it happens again: 1) post your `emerge --info' output in a comment. 2) attach the entire sync log to this bug report.
Created attachment 392848 [details] emerge --sync from frontend, & actual machine + emerge --info And that helps to determine something that is faster checked by using emerge -1 xxdi???? Well ok.
And to be sure: it still fails: # emerge -1 xxdi Calculating dependencies... done! >>> Verifying ebuild manifests !!! Digest verification failed: !!! /usr/portage/dev-util/xxdi/metadata.xml !!! Reason: Failed on SHA256 verification !!! Got: 4584cfc74776dcb4d6976a3686a249537cb81b1f037d95bece3b0f63dba016dc !!! Expected: 503c83eefd31a7c19429e12befc0a41c5e773557e35a10cfce23a618e68e6392 >>> Emerging (1 of 1) dev-util/xxdi-1.0.0::gentoo !!! Digest verification failed: !!! /usr/portage/dev-util/xxdi/metadata.xml !!! Reason: Failed on SHA256 verification !!! Got: 4584cfc74776dcb4d6976a3686a249537cb81b1f037d95bece3b0f63dba016dc !!! Expected: 503c83eefd31a7c19429e12befc0a41c5e773557e35a10cfce23a618e68e6392 >>> Failed to emerge dev-util/xxdi-1.0.0 * * The following package has failed to build or install: * * (dev-util/xxdi-1.0.0:0/0::gentoo, ebuild scheduled for merge) *
(In reply to Nico Baggus from comment #2) > Created attachment 392848 [details] > emerge --sync from frontend, & actual machine + emerge --info > > And that helps to determine something that is faster checked by using emerge > -1 xxdi???? Yes, because on the side of the CVS repo, nothing is wrong, but on your end there is a problem, so knowing which rsync mirror is responsible is what we need to know.
total 12 -rw-r--r-- 1 root root 2372 Dec 24 2013 Manifest -rw-r--r-- 1 root root 1043 Oct 11 2013 metadata.xml -rw-r--r-- 1 root root 627 Dec 24 2013 xxdi-1.0.0.ebuild
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 DIST xxdi-1.0.0.tar.gz 8039 SHA256 5279cd356a680ef22dafc13a8b674eafa81c2bc82f57b38b04059b16c046f1b0 SHA512 ebf026f61f0b0a339e3dfa5c9dd6a819ef23f0d29948073cbf5f6ae9668e68a7dd903f695ab5a824494f8424dad8b79aace5742bc23484a25303a15aa32ab698 WHIRLPOOL ed3199facbd8cdef6f37e8e595d6c91d994e0fdbe449ab95e4db6bb95e1ae6f0ed0c8650281a7aab9de7d22e8ef9f96dfb9383716043a99ca4c6ebbfd815248a EBUILD xxdi-1.0.0.ebuild 627 SHA256 be4677a2cb9c211c04f121df3bdcb7bc588b241a3009fb636959378f0345eed8 SHA512 5fdc17a359b3a5f7bc82fc81d238db80671cd8182015ae2081f3f28aa3507e1cca8f3984b48affb5578ac6a1b079ad2a4d2dbf41df9e656b02951f77ca853938 WHIRLPOOL 5e17f42f038773157f1dd93608b0b1bc0ae6101a196dc0177a0aeb272081b957f415ffc44bbd33c4d1a1410516f94afdfe882580891f0e5849d061dcd60df925 MISC ChangeLog 848 SHA256 71999ffa608e8e735c5ced12642552d29de84dce1d19d4a9fe8b0096fdb4b580 SHA512 f7306c9f9bf7abad0a7148910b0d04b2bc9d4a11a97d6fe48aa142986a86fde6e664635f0192823fde0edb8b21f7697ce7dfd2ecb79ed5d0455caa65505e3f34 WHIRLPOOL 1939b90a77ac301cd646fa14f41c898dce9d93e172394afafc1f657ac0da9231defb234fdbe033ed22e1ef1968c9b248a261cc4c3378b67704f5e0df0d461c61 MISC metadata.xml 1043 SHA256 503c83eefd31a7c19429e12befc0a41c5e773557e35a10cfce23a618e68e6392 SHA512 04a82a2ac61334258ae242fc3fa0a9f3d35fe9763b6af5940ddc4ded81ecf24815904f448d94415abd91784e75549eb236e5a0056ad48310d677d433186dc01e WHIRLPOOL 942c7978222d9bf08f924c04f0b83b172e5f6ca4536a5800ac401636e9f39b53c42b605a2c7c96632fbdfcb1d23c5d5f1ae9029855f801e6b198df9a1799d520 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBCAAGBQJSuYN/AAoJELp701BxlEWfbtgP/iTwCqN7e4wEV64zT7xADNCt rFLzsrWZ+ZwJMCBP4ugcD1IR90J+HBSQqAwdjo4rwFIXwQqLWTYa2nkEhIW9pwYl 5nTQ6ZbbvO3EHeN6Ry+S0C6c/PGgxg1d54ajahXNiCutlpzW6XhNE7JRzsN663NX Ygz0D4OsVESeAttGxVupzdMIK6YjX7n77J7er4oCzpSrPqd7BdrzWvxZEenFsUA6 GO2Th+oJFt7DDW7wKSUawjnpxxqWhTmxbwai5+UsH8XX/G1qhVWrUGLlAimCzUXn eAyQZ2cxt+u8S+wsh6ixw2gf6VsvwSwpQgXo5JBAdArr+osEtZ3DjjwYntB8vjL8 XkBQXzttUBQU29GvmU6560taUF7+ClX+aTkaH3GMghxPdTGQiR5ES+2ydQmb8CWZ WuSHl4wliw0PtZJ9w7U8LBWOlGCOD4sJsVk33BnjI+R3AQ+WeoOT4hdr72jWTvbZ XVGNaHmEB7hFcTmLKKXkxlBuCJC9mQSl1wIkK05BrLicBBSXUlFzKzNu7Lja8oD6 QO5PcXQdjB5GoM9ZwCoUBwAlRiZTCIL+7Pr1bY8IwaDAP3RMMDjPuLccMvbSVZWr CN6DSIaQovnuISy3psw23hJPiGqsRPZNk189uA/C0Y/SPMd+008o3fHm0FYE3S1y WIwA/AEmdxGIgp4lelqQ =zjFn -----END PGP SIGNATURE-----
the meta.xml contains some binary values..
I removed the binary metadata file, resynced again and now the ebuild works. Somehow this file was appearantly stored corrupted but it was never noticed or corrected in the year and a half that it is in existentce. Maybe an option for a forced download, or rsync WITH content verification is an option?
