> On Nov 15, 2015, at 12:43, Peter Humphrey <pe...@prh.myzen.co.uk> wrote: > > On Sunday 15 Nov 2015 12:22:39 Matti Nykyri wrote: >>> On Nov 15, 2015, at 11:59, Alan Mackenzie <a...@muc.de> wrote: > --->8 >>> Three days later. I'm still getting this error message, but with a >>> nasty >>> twist in the tail. emerge -puND @world reports (amongst others) the >>> >>> following update: >>> [ebuild R ] sys-apps/busybox-1.23.1-r1 USE="-pam*" >>> >>> , and the error message I get on actually trying to start the update is >>> >>> !!! Digest verification failed: >>> !!! /usr/portage/sys-apps/busybox/busybox-9999.ebuild >>> !!! Reason: Filesize does not match recorded size >>> !!! Got: 8493 >>> !!! Expected: 8580 >>> >>> . Why is the build system looking at the digest for version 9999 when >>> it >>> should be rebuilding version 1.23.1-r1? >> >> Well it's not. It just checks all the manifests and complains about >> errors. It doesn't affect the building of 1.23.1-r1. > > I'm getting the same thing as Alan, and have been for several days. > >> If I were you I'ld download the latest portage snapshot. That should take >> care of any remaining issues. Is your portage upto date? > > My portage is sync'd daily, so it shouldn't need a whole new snapshot.
Sunc doesn't necessarily sync everything and if some random files are out of sync you either need to update them manually or get a new snapshot. I doubt the server/mirror is messed up, but you could try changing that. Downloading a new snapshot isn't that big a deal and that should definitely fix everything, so why not try that first? You may also inspect each package and remanifest those that have problems (ebuild manifest). If you are certain that nobody has been fingering your ebuilds. -- -M
