Summary: | emerges for automake since 1.8.5-r1 upgrade was released reporting corrupt or incomplete | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Michael E. Adams <meadams> |
Component: | [OLD] Core system | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED WORKSFORME | ||
Severity: | blocker | CC: | mschulkind |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Michael E. Adams
2004-08-21 06:47:04 UTC
I should add that the problem first occurred after performing an: emerge -uD system All fine here, but the datapipe mirror has been having some trouble today. Remove datapipe from your mirrors list then: rm /usr/portage/distfiles/automake* emerge automake try a different mirror ... digest is fine Ok, I edited my /etc/make.config to remove datapipe as suggested.rm Then: /usr/portage/distfiles/automake* emerge automake And automake emerged just fine. But... I did an emerge sync and and emerge -uD world and ended up with: emerge -uD world Calculating world dependencies ...done! >>> emerge (1 of 1) x11-libs/qt-3.3.3 to / !!! File is corrupt or incomplete. (Digests do not match) >>> our recorded digest: 3e0a0c8429b0a974b39b5f535ddff01c >>> your file's digest: 5e2a4a5896cd6fd51d12dfe0fddb9b69 !!! File does not exist: /usr/portage/distfiles//qt-x11-free-3.3.3.tar.bz2 I may be paranoid, but is something bad happening here? I will submit a bug for this to document it also. Regards Once again, as I said, remove datapipe from your list of mirrors. It is broken. Matthew, I did remove datapipe. I see the listing I supplied has it there, but it is removed - which is why I am concerned. Again, I am not using the datapipe mirror. I also am not able to emerge mirrorselect - again not from datapipe! Now what? When you're downloading the packages, does it get the first 200 or so bytes from one mirror and the rest from another? Does the beginning of the file have HTML in it when it has a bad digest? Matthew, I don't know how to tell. If I do an emerge -v mirrorselect here is what I get: emerge --verbose mirrorselect Calculating dependencies ...done! >>> emerge (1 of 2) net-analyzer/netselect-0.3 to / !!! File is corrupt or incomplete. (Digests do not match) >>> our recorded digest: 3a3714946db2458e5db3d55373057ef2 >>> your file's digest: 78e64e3d5971677705dcf87a0a017d86 !!! File does not exist: /usr/portage/distfiles//netselect-0.3.tar.gz I Should have sent this: emerge -v =x11-libs/qt-3.3.3 Calculating dependencies ...done! >>> emerge (1 of 1) x11-libs/qt-3.3.3 to / !!! File is corrupt or incomplete. (Digests do not match) >>> our recorded digest: 3e0a0c8429b0a974b39b5f535ddff01c >>> your file's digest: 5e2a4a5896cd6fd51d12dfe0fddb9b69 !!! File does not exist: /usr/portage/distfiles//qt-x11-free-3.3.3.tar.bz2 Delete the files in question and try that again. Matthew, Yes, Ok, I deleted the files and emerged again, and was successful. Can you explain, or point me to a document that explains how emerge is using md5 and is doing its security checks. I didn't think that the portage tree on my system could be the source of the problem. Thanks. /usr/portage/distfiles is not part of the portage tree. That is where portage downloads all the packages to. It does not come in with "emerge sync" Matthew, Gotcha. I understand. Thanks again. Regards |