From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003
Description of problem:
While running the up2date GUI installer, an MD5 error message was displayed in
the console. However the final summary page indicated all installed correctly.
The error message is:
[root@ferdinand conf]# up2date
error: rpmts_HdrFromFdno: MD5 digest: BAD
Expected(46dbe5e58ff89f16978689c3385bde11) != (17751cb76fa32751f65e5ae2be02b3d5)
The packages installed where:
The Red Hat Update Agent has finished installing
the following packages successfully:
The last entries in /var/log/up2date are attached.
Version-Release number of selected component (if applicable):
Created attachment 81367 [details]
/var/log/up2date file - last entries
looks like a librpm issue, reassigning to rpm
The error message is coming from mozilla:
Header V3 DSA signature: OK, key ID db42a60e
Header SHA1 digest: OK (fe02024782cca0c9e569000546d27b01af163730)
MD5 digest: OK (46dbe5e58ff89f16978689c3385bde11)
V3 DSA signature: OK, key ID db42a60e
rpm -Kvv mozilla-1.0.1-26.i386.rpm
say? If that passes, then there are no obvious
(to me) rpmlib issues.
I am confused, however, why the MD5 is being calculated
at all, as there is a DSA signature on the package. The
choice of what package signatures/digests to calculate
when is an up2date, not rpm, coding issue.
So what is the rpmlib issue?
I can't perform the "rpm -Kvv" command on the rpm package in /var/spool/up2date.
As shown in the attached log, the package was deleted after the install.
Sounds like you just got a corrupted package on download. up2date runs
a md5sum check on packages to see if they are complete and not corrupt.
If this check fails, you get a error message like the above, and then
up2date downloads the package again. So the message is a warning,
and is harmless.