I cannot successfully use 'emerge' to build 'apr-util' because of a fault either in the manifest or in the other files: vm root # uname -a Linux vm.yewbarrow.net 2.4.26-bytemark-uml-20040706-1 #1 Tue Jul 6 09:37:31 BST 2004 i686 UML User Mode Linux GNU/Linux vm root # cat /etc/gentoo-release Gentoo Base System version 1.4.16 vm root # emerge --sync >>> starting rsync with rsync://80.68.81.149/gentoo... >>> checking server timestamp ... receiving file list ... 1 file to consider Number of files: 1 Number of files transferred: 0 Total file size: 32 bytes Total transferred file size: 0 bytes Literal data: 0 bytes Matched data: 0 bytes File list size: 32 Total bytes written: 187 Total bytes read: 68 wrote 187 bytes read 68 bytes 510.00 bytes/sec total size is 32 speedup is 0.13 >>> >>> Timestamps on the server and in the local repository are the same. >>> Cancelling all further sync action. You are already up to date. >>> vm root # emerge apr-util Calculating dependencies ...done! >>> emerge (1 of 1) dev-libs/apr-util-0.9.6-r2 to / >>> md5 files ;-) apr-util-1.1.2.ebuild !!! Digest verification Failed: !!! /usr/portage/dev-libs/apr-util/apr-util-0.9.6-r2.ebuild !!! Reason: Filesize does not match recorded size >>> Please ensure you have sync'd properly. Please try 'emerge sync' and >>> optionally examine the file(s) for corruption. A sync will fix most cases. vm root # vm root # ls -l /usr/portage/dev-libs/apr-util/apr-util-0.9.6-r2.ebuild -rw-r--r-- 1 root root 2025 Sep 19 00:05 /usr/portage/dev-libs/apr-util/apr-util-0.9.6-r2.ebuild vm root # grep apr-util-0.9.6-r2.ebuild /usr/portage/dev-libs/apr-util/Manifest MD5 527ebb4c794d390bfe6ef1c37b3f6a1e apr-util-0.9.6-r2.ebuild 2024 Reproducible: Always Steps to Reproduce: 1. emerge apr-util 2. 3. Actual Results: Calculating dependencies ...done! >>> emerge (1 of 1) dev-libs/apr-util-0.9.6-r2 to / >>> md5 files ;-) apr-util-1.1.2.ebuild !!! Digest verification Failed: !!! /usr/portage/dev-libs/apr-util/apr-util-0.9.6-r2.ebuild !!! Reason: Filesize does not match recorded size >>> Please ensure you have sync'd properly. Please try 'emerge sync' and >>> optionally examine the file(s) for corruption. A sync will fix most cases. Expected Results: Rebuilt 'apr-util' 'emerge sync' doesn't fix the problem.
Try rm /usr/portage/metadata/timestamp* before emerge sync'ing again. It doesn't sync if the remote sync server has the same timestamp. Also, consider that the remote server might have a borked copy of that file.
Unable to reproduce the broken digest here. Please emerge --sync and try again.
