Summary: | emerge fails: md5sum in digest-cl-defsystem3-3.3i-r4 doesn't match md5sum of gz file in /usr/portage/distfiles | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Walt Rarus <walrus06437> |
Component: | New packages | Assignee: | Matthew Kennedy (RETIRED) <mkennedy> |
Status: | RESOLVED NEEDINFO | ||
Severity: | major | CC: | robertc96 |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Walt Rarus
2004-08-03 06:18:03 UTC
Duh!!! Well, if I had hidden the original digest and then tried reconstructing a new one, the process would have succeeded. This doesn't alter the fact that emerge sync puts out a bogus digest-cl-defsystem3-3.i-r4 requiring users to manually kill and replace it. Walt, This was my fault. I committed the wrong source file in such a way repoman didn't pick it up, but this was corrected shortly after. You might have been unlucky enough to have synced during that window. Its also possible that slow mirrors exacerbated the problem. I double checked just now though: $ cat /usr/portage/dev-lisp/cl-defsystem3/files/digest-cl-defsystem3-3.3i-r4 MD5 07622698648453794ff4d955db07af94 cl-defsystem3_3.3i+cvs.2004.07.18.1.tar.gz 75862 $ wget -q -O- http://ftp.ibiblio.org/pub/Linux/distributions/gentoo/distfiles/cl-defsystem3_3.3i+cvs.2004.07.18.1.tar.gz |md5sum 07622698648453794ff4d955db07af94 - $ sudo emerge cl-defsystem3 --fetchonly Calculating dependencies ...done! >>> emerge (1 of 1) dev-lisp/cl-defsystem3-3.3i-r4 to / >>> Previously fetched file: cl-defsystem3_3.3i+cvs.2004.07.18.1.tar.gz MD5 ;-) >>> md5 src_uri ;-) cl-defsystem3_3.3i+cvs.2004.07.18.1.tar.gz $ md5sum /usr/portage/distfiles/cl-defsystem3_3.3i+cvs.2004.07.18.1.tar.gz 07622698648453794ff4d955db07af94 /usr/portage/distfiles/cl-defsystem3_3.3i+cvs.2004.07.18.1.tar.gz $ Have you tried an emerge sync since then? It should have the right digest now. *** Bug 59145 has been marked as a duplicate of this bug. *** please re-open if the problem is not fixed I see no need to reopen. I've now got a correct digest dated 8/2/04 (which is *before* my initial bug report on 8/3/04 :) which must have come down on an emerge sync. Thanks for your efforts. |