This morning I did a sync of the portage tree. When I do emerge -avuND world I get 2 messages about consolekit: Calculating dependencies - * Digest verification failed: * /usr/portage/sys-auth/consolekit/consolekit-0.3.0-r2.ebuild * Reason: Filesize does not match recorded size * Got: 3088 * Expected: 3016 \ * Digest verification failed: * /usr/portage/sys-auth/consolekit/consolekit-0.4.1.ebuild * Reason: Filesize does not match recorded size * Got: 2965 * Expected: 2894 First I thought this might me a fault in transfer. So I deleted /usr/portage/metadata/timestamp.chk and moved the ebuilds that gave errors. THen I did a sync again: emerge --sync When doing emerge -avuND world again I get the same message about consolekit. The server address is: Server Address : 134.68.220.97 Server Address : 88.198.83.249/29 seems to have the same result. So this is probably an issue with the ebuild (forgotten ebuild consolekit *.ebuild digest?) Or there is something fishy going on? I will wait until I hear more about this. Reproducible: Always Steps to Reproduce: 1. emerge --sync 2. emerge -av consolekit , ... 3. Actual Results: Calculating dependencies - * Digest verification failed: * /usr/portage/sys-auth/consolekit/consolekit-0.3.0-r2.ebuild * Reason: Filesize does not match recorded size * Got: 3088 * Expected: 3016 \ * Digest verification failed: * /usr/portage/sys-auth/consolekit/consolekit-0.4.1.ebuild * Reason: Filesize does not match recorded size * Got: 2965 * Expected: 2894 Expected Results: This message shouldn't be there.
Try resyncing now - the manifest commit appears to have been done after the rsync mirrors picked up the first part of the change (sometimes CVS is slow enough to make that matter)
(In reply to comment #1) > Try resyncing now - the manifest commit appears to have been done after the > rsync mirrors picked up the first part of the change (sometimes CVS is slow > enough to make that matter) > I did the resync and it fixed the issue :) Thanks