dev-java/java-config-2.0.27-r1 and dev-java/java-config-1.3.1-r1 produce a digest verification failure. emerge -f gives these error messages: >>> Emerging (12 of 18) dev-java/java-config-2.0.27-r1 to / * java-config-2.0.27.tar.bz2 MD5 ;-) ... [ ok ] * java-config-2.0.27.tar.bz2 RMD160 ;-) ... [ ok ] * java-config-2.0.27.tar.bz2 SHA1 ;-) ... [ ok ] * java-config-2.0.27.tar.bz2 SHA256 ;-) ... [ ok ] * java-config-2.0.27.tar.bz2 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ !! ] !!! Digest verification failed: !!! /usr/portage/dev-java/java-config/files/java-config-2.profiled !!! Reason: Filesize does not match recorded size !!! Got: 762 !!! Expected: 768 !!! Fetch for /usr/portage/dev-java/java-config/java-config-2.0.27-r1.ebuild failed, continuing... >>> Emerging (13 of 18) dev-java/java-config-1.3.1-r1 to / * java-config-1.3.1.tar.bz2 MD5 ;-) ... [ ok ] * java-config-1.3.1.tar.bz2 RMD160 ;-) ... [ ok ] * java-config-1.3.1.tar.bz2 SHA1 ;-) ... [ ok ] * java-config-1.3.1.tar.bz2 SHA256 ;-) ... [ ok ] * java-config-1.3.1.tar.bz2 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ !! ] !!! Digest verification failed: !!! /usr/portage/dev-java/java-config/files/java-config-2.profiled !!! Reason: Filesize does not match recorded size !!! Got: 762 !!! Expected: 768 !!! Fetch for /usr/portage/dev-java/java-config/java-config-1.3.1-r1.ebuild failed, continuing...
*** Bug 145057 has been marked as a duplicate of this bug. ***
same here .. Should really CHECK this type of thing before committing ...
I really don't know how this happened. The difference in the file between what I had in my checkout and what was in cvs was: -# $Header: /var/cvsroot/gentoo-x86/dev-java/java-config/files/java-config-2.profiled,v 1.3 2006/08/25 02:13:17 nichoj Exp $ +# $Header: /var/cvsroot/gentoo-x86/dev-java/java-config/files/Attic/java-config-2.profiled,v 1.3 2006/08/25 02:13:17 nichoj Exp $ In any event, I redigest it, so it is fixed in CVS now. Give it a few hours to hit your local rsync mirror.
*** Bug 145075 has been marked as a duplicate of this bug. ***
*** Bug 145076 has been marked as a duplicate of this bug. ***
(In reply to comment #3) > I really don't know how this happened. The difference in the file between what > I had in my checkout and what was in cvs was: > > -# $Header: > /var/cvsroot/gentoo-x86/dev-java/java-config/files/java-config-2.profiled,v 1.3 > 2006/08/25 02:13:17 nichoj Exp $ > +# $Header: > /var/cvsroot/gentoo-x86/dev-java/java-config/files/Attic/java-config-2.profiled,v > 1.3 2006/08/25 02:13:17 nichoj Exp $ > > In any event, I redigest it, so it is fixed in CVS now. Give it a few hours to > hit your local rsync mirror. > Any change in file content/size (even just one character) is going to affect the hash codes (MD5, SHA256), and drastically at that. It would probably help if something was set up to automatically run redigest all files in a package upon arrival of new/updated file(s) so that this error could be avoided in the future. Also, these errors are easily bypassed by filling the expected values into the Manifest in place of the invalid ones, but that just defeats point of having the size and checksum in the Manifest file for validation.
