Bug 431403
Summary: | probable wrong libgcc-4.1.2-33.i386.rpm checksum in FC8 primary.xml.gz | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Mark Abraham <mark.j.abraham> |
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | low | ||
Version: | 8 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-06-03 17:21:21 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Mark Abraham
2008-02-04 08:30:13 UTC
Enhancing the above, you can observe this mismatch between the contents of the metadata file here http://mirrors.kernel.org/fedora/releases/8/Everything/i386/os/repodata/primary.xml.gz and running md5sum on the RPM file here http://mirrors.kernel.org/fedora/releases/8/Everything/i386/os/Packages/libgcc-4.1.2-33.i386.rpm Duh. It's not an MD5 sum. sha1sum is correct for this RPM and the metadata file. That scotches my theory on what is causing the problem, but doesn't solve it. Can you attach /tmp/anaconda.log to this bug report after you get to the error message in question? (In reply to comment #3) > Can you attach /tmp/anaconda.log to this bug report after you get to the error > message in question? Unfortunately, no. The machine on which I was attempting the above install has now had an FC8 system installed on it via the LiveCD with no problems, and the partition where that logfile would have been written has been over-written. The current /tmp/anaconda.log is also not helpful, since it doesn't mention libgcc. I'll remember to keep anaconda.log files in future, though. I'd have to do some googling to work out how you can recover a .log file from a machine on which an install failed to complete, but I guess a rescue disk would give you a chance. Thanks! Mark Without error logs, there's not much we can do. Closing this; please reopen if you either run into the bug again or manage to recover the log file. |