Qian Qiao schreef: > On 11/2/05, Martins Steinbergs <[EMAIL PROTECTED]> wrote: > >> 002617 !!! Digest verification Failed: 002618 !!! >> /usr/portage/dev-python/pyrex/pyrex-0.9.3.1.ebuild 002619 !!! >> Reason: Filesize does not match recorded size 002620 002621 >>> >> Please ensure you have sync'd properly. Please try 'emerge sync' >> and 002622 >>> optionally examine the file(s) for corruption. A >> sync will fix most cases. > > > You can either wait for a re-sync, or do a:- > > # ebuild /path/to/the/ebuild digest >
That's true, but redigesting official Portage files manually is a *very* bad habit to get into, and I would strongly recommend against it. The whole point of Portage's digesting and digest verification is to ensure/verify that the files you have received have not been tampered with/contain no errors. If the official digest doesn't match the file, *something is wrong*, and unless you (generic 'you') happen to be in a position to know what that is, and because you know, you can safely override Portage (which is what a manual digest does), you in fact cannot safely override Portage, and should not do so. Patience is a virtue. Wait, and sync again, for official files. Overlay files are a different story. For all you know, the 'problem' is that the mirrors have not finished syncing yet, and you only have half the distfile/the wrong distfile. So when you attempt to emerge, the emerge will fail because there's actually something wrong with the tarball, and then you've screwed your digest and have to sync again anyway to fix it, and you didn't get any result anyway (the app has not emerged). Just wait. Portage fixes itself pretty quick. Holly -- gentoo-user@gentoo.org mailing list
