>>> Emerging (1 of 3) app-editors/vim-core-7.0.235 to / * vim-7.0-r1.tar.bz2 RMD160 ;-) ... [ ok ] * vim-7.0-r1.tar.bz2 SHA1 ;-) ... [ ok ] * vim-7.0-r1.tar.bz2 SHA256 ;-) ... [ ok ] * vim-7.0-r1.tar.bz2 size ;-) ... [ ok ] * vim-7.0-gentoo-patches-r1.tar.bz2 RMD160 ;-) ... [ ok ] * vim-7.0-gentoo-patches-r1.tar.bz2 SHA1 ;-) ... [ ok ] * vim-7.0-gentoo-patches-r1.tar.bz2 SHA256 ;-) ... [ ok ] * vim-7.0-gentoo-patches-r1.tar.bz2 size ;-) ... [ ok ] * vim-patches-7.0.235.tar.gz RMD160 ;-) ... [ ok ] * vim-patches-7.0.235.tar.gz SHA1 ;-) ... [ ok ] * vim-patches-7.0.235.tar.gz SHA256 ;-) ... [ ok ] * vim-patches-7.0.235.tar.gz size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ !! ] !!! Digest verification failed: !!! /usr/portage/app-editors/vim-core/ChangeLog !!! Reason: Filesize does not match recorded size !!! Got: 34344 !!! Expected: 34310
pioto updated the changelogs to app-editors/{vim-core,vim,gvim} without regenerating the digest.
Fixed in CVS. Please wait approx. one hour and do an emerge --sync again, or use `ebuild /path/to/ebuild/ digest'.
Thanks. Same problem with app-editors/vim-7.0.235
> app-editors/{vim-core,vim,gvim} Oops, sorry, never saw that.
Sorry all, I haven't been doing much dev-ing recently, and I forgot that ChangeLog's are in the Manifest too... That'll teach me to skip repoman even for the small stuff.
*** Bug 177137 has been marked as a duplicate of this bug. ***
again today with gvim on amd64 !!! Digest verification failed: !!! /usr/portage/app-editors/gvim/gvim-7.0.235.ebuild !!! Reason: Filesize does not match recorded size !!! Got: 1182 !!! Expected: 1107
Huh? I know I didn't mess it up this time. Repoman says all is well in my CVS checkout. So, either repoman is busted, or you need to emerge --sync again.
I have this error just after an emerge --sync. We'll see tomorrow.
I think maybe this is just the non-atomicness of CVS commits showing how much it can suck. The "got" size is what the current ebuild in CVS is. The Manifest was clearly updated at around the same time (according to cvs logs), but apparently that file's commit just didn't quite make it in time for the latest update of the rsync mirrors... Try downloading the Manifest file from here: http://sources.gentoo.org/viewcvs.py/*checkout*/gentoo-x86/app-editors/gvim/Manifest?rev=1.332 If that doesn't work, something is weird with portage. If it does, then CVS just sucks.
Works fine with this Manifest. I don't have error anymore with "emerge -DauvN world" I don't need gvim, I just wanted to report the error to you. I do emerge --sync every night, and I didn't have this error before this night. Thanks.
