On May 23, 2011, at 11:27 AM, Orion Poplawski wrote: > On 05/20/2011 04:27 PM, Orion Poplawski wrote: >> I'm still looking into this, but I figured I'd post what I have since it is >> completely reproducible. If I enable the rpmforge repo when doing my SL6 >> install after the package install process the rpm database is corrupted, >> e.g.: >> >> # rpm -qa >> error: rpmdbNextIterator: skipping h# 769 Header V4 DSA/SHA1 Signature, key >> ID >> 192a7d7d: BAD >> error: rpmdbNextIterator: skipping h# 259 Header V4 DSA/SHA1 Signature, key >> ID >> 192a7d7d: BAD >> error: rpmdbNextIterator: skipping h# 518 Header V4 DSA/SHA1 Signature, key >> ID >> 192a7d7d: BAD >> error: rpmdbNextIterator: skipping h# 8 Header V4 DSA/SHA1 Signature, key ID >> 192a7d7d: BAD >> .... >> >> I am only installing transcode and unrar, which brings in the following other >> rpmforge package (plus some more sl packages): >> >> Installing dropbox-1.1.27-1.el6.rf.x86_64 > > This is the problem (I think): >
The above are digital signature failures, not filtering problems. You can try adding --nosignature, and I suspect you will then see a digest failure. You can then add --nodigest, and then you may see a "header sanity check" failure. You can then try disabling the "header sanity check" with --nohdrchk and attempt to proceed with all integrity checks disabled if you wish. To identify the root cause of the problem (e.g. DSA may be broken, or SHA1 might be broken, and the sanity check can catch some but not all brokenness with details). Otherwise, rpm --rebuilddb will discard those headers, and you need to identify what needs replacing. Sometimes rpm -qa -vv helps do that. Also comparing rpm -qa with /var/log/rpmpkgs can sometimes identify the damage. But filtering dependencies simply isn't going to help "fix" the errors above. hth 73 de Jeff
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ users mailing list users@lists.rpmforge.net http://lists.rpmforge.net/mailman/listinfo/users
