Bug 52329
| Summary: | up2date indicates that it installs packages with md5sum mismatches. | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Public Beta | Reporter: | Need Real Name <bharath> |
| Component: | up2date | Assignee: | Adrian Likins <alikins> |
| Status: | CLOSED NOTABUG | QA Contact: | Jay Turner <jturner> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | roswell | CC: | gafton, mihai.ibanescu, srevivo |
| 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: | 2001-08-24 18:46:44 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
Need Real Name
2001-08-22 20:33:31 UTC
Okay, can you have a look at the file sizes? Can you look at the beginning or at the end of a corrupted file and see if it looks like data or it has some human-readable stuff attached? I will try to duplicate this too. We (Red Hat) should really try to fix this before next release. Here are the file sizes:
[bharath@yakuza up2date]$ ls -l e*rpm | awk '{print $5 " " $9}'
8085113 emacs-20.7-41.i386.rpm
974973 emacs-nox-20.7-41.i386.rpm
1096255 emacs-X11-20.7-41.i386.rpm
729412 exmh-2.4-2.noarch.rpm
The beginning of the file looks ok (file magic) I can read some text, the end
looks like data.
These are perfectly valid file sizes. Could you please run md5sum on the files too? Thanks. [bharath@yakuza up2date]$ md5sum e*rpm 082a935d9a4e4b6b4dcb3f13efe6da9f emacs-20.7-41.i386.rpm c5418d77e067a681115c83508b6bf46c emacs-nox-20.7-41.i386.rpm 0ded75ccf179251a7d9428fad2881641 emacs-X11-20.7-41.i386.rpm 1df8b1a082a04372ba8ad954752648e2 exmh-2.4-2.noarch.rpm I'm not able to replicate the invalid MD5 sums here in the office, which would lead me to believe that it was probably a dirty connection which resulted in the corrupt RPMs. The bigger issue is if up2date should check the MD5 sum of everything that it downloads and retry stuff that fails X times. Probably a pretty good enhancement request. That would be good. 1. Check each package downloaded for md5sum mismatch 2. Retry if user says ok 3. Install any packages which doesn't have conflicts or corruption if user decides not to retry instead of quitting completely 4. If files are saved to disk, check md5sum before using them. Download if needed. md5sum signatures of the packages do get checked in normal operation, but not if "--nosig" is turned on. I'll take a look at seperating these checks into two steps so that md5sum sigs always get checked and "--nosig" only skips the gpg sig check. This is a bit of a "beta only" circumstance though... |