emerge gnet Calculating dependencies... done! >>> Verifying ebuild manifests !!! Digest verification failed: !!! /usr/gentoo/portage/net-libs/gnet/files/gnet-2.0.8-define-location.patch !!! Reason: Failed on RMD160 verification !!! Got: 568b80fb1e20c3be8ad5f524b8b0f7e29d60bec8 !!! Expected: f1ea07a68a0d90ebb6d83fda68b2e478871e3ca9 I synced portage tree before to submit report Reproducible: Always
Please attach the emerge-sync log.
last sync from emerge.log (I don't know if there's other more specific log file) 1345551022: Started emerge on: Aug 21, 2012 19:10:21 1345551022: *** emerge --misspell-suggestions=n --sync 1345551022: === sync 1345551022: >>> Starting rsync with rsync://209.177.148.226/gentoo-portage 1345551962: === Sync completed with rsync://209.177.148.226/gentoo-portage 1345551965: *** terminating. the localtime is in vietnam bug was filled about 20 minuts later
Have you checked if a new rsync fixes the issue?
I synced 20 minuts ago 1345578040: Started emerge on: Aug 22, 2012 02:40:40 1345578040: *** emerge --misspell-suggestions=n --sync 1345578040: === sync 1345578041: >>> Starting rsync with rsync://176.28.50.119/gentoo-portage 1345578259: === Sync completed with rsync://176.28.50.119/gentoo-portage 1345578260: *** terminating. But still: emerge gnet Calculating dependencies... done! >>> Verifying ebuild manifests !!! Digest verification failed: !!! /usr/gentoo/portage/net-libs/gnet/files/gnet-2.0.8-define-location.patch !!! Reason: Failed on RMD160 verification !!! Got: 568b80fb1e20c3be8ad5f524b8b0f7e29d60bec8 !!! Expected: f1ea07a68a0d90ebb6d83fda68b2e478871e3ca9 P.S.: This was why I precised in my initial bug report message that I synced before open bug. It was to check that syncing didn't fix the things.
-AUX gnet-2.0.8-define-location.patch 519 RMD160 f1ea07a68a0d90ebb6d83fda68b2e478871e3ca9 SHA1 4c44374694ff25336f7acbe3e93536e6291fa475 SHA256 65824a271eb64d34d227c8f5865586790fe3a3c943fef65ae71f8f94ef471fe2 +AUX gnet-2.0.8-define-location.patch 519 SHA256 65824a271eb64d34d227c8f5865586790fe3a3c943fef65ae71f8f94ef471fe2 SHA512 a0d20e0f17d8247509a8e78b2571910167f0815679f0f30c75fc3ed69a31a20e8e70fb7005febdea1b7f81ef8b30603d99cffb522af185d163d2e9bb12a6e12f WHIRLPOOL 47e6f38e54a7b802c3b61b668c21b6a4203e50810778f2c712b5af2ad53271d246f38c5053f9ff073d5884ec2fdd841edd130db46afaa1defc067679af61c954 The patch in question didn't change, but it seems the Manifest was never updated.