Bug 712081

Summary: md5 mismatch on mesa-dri-llvmcore...drpm
Product: [Fedora] Fedora Reporter: John Reiser <jreiser>
Component: deltarpmAssignee: Jonathan Dieter <jdieter>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: jdieter, robatino
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-29 17:54:58 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description John Reiser 2011-06-09 12:59:15 UTC
Description of problem: "yum upgrade" via deltarpm
  from:  mesa-dri-llvmcore-7.11-0.9.20110509.0.fc15
    to:  mesa-dri-llvmcore-7.11-0.11.20110525.0.fc15.i686
gets an md5 mismatch when rebuilding the .rpm from the .drpm.

Version-Release number of selected component (if applicable):
deltarpm-3.6-0.6.20110223git.fc15.i686



How reproducible: haven't tried


Steps to Reproduce:
1. Install f15 from release DVD.
2. yum update
3.
  
Actual results:
/var/cache/yum/i386/15/updates/deltas/mesa-dri-llvmcore-7.11-0.9.20110509.0.fc15_7.11-0.11.20110525.0.fc15.i686.drpm: md5 mismatch of result
<delta rebuild>                                                 | 243 MB     02:08     
Error rebuilding rpm from mesa-dri-llvmcore-7.11-0.9.20110509.0.fc15_7.11-0.11.20110525.0.fc15.i686.drpm! Will download full package.

Expected results: no md5 mismatch


Additional info:
kernel-PAE-2.6.38.6-26.rc1.fc15.i686 with 8GB RAM, system very lightly loaded, no swap space used

Comment 1 Jonathan Dieter 2011-06-09 13:46:18 UTC
This means the deltarpm didn't build back into a byte-for-byte copy of the original rpm.  I've just applied the deltarpm above against the original -0.9.20110509 rpm in the repositories, and there are no errors, so that seems to mean you had a bit-flip either in memory or on the hard drive.

If you can reproduce the error (by downgrading mesa-dri-llvmcore and then updating again), I'll happily take a look again.  Otherwise, I'll close this in a week or so.

Comment 2 Jonathan Dieter 2011-06-09 19:26:25 UTC
Sorry, Andre, I just saw that you canceled the needinfo on this.  Have you seen this bug on one of your systems?

Comment 3 Andre Robatino 2011-06-09 19:34:35 UTC
I didn't deliberately cancel the needinfo, just subscribed to the bug. Sorry about that.

Comment 4 Jonathan Dieter 2011-06-29 17:54:58 UTC
Closing as it seems this was a one-time fluke.  Please reopen if you hit this again.