On 05/23/2011 09:40 AM, Jeff Johnson wrote:
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):
But filtering dependencies simply isn't going to help "fix" the errors above.
It can and does. Adding --excludepkgs=dropbox to my rpmforge kickstart repo
line fixes the problem. The problem is that dropbox is getting installed
instead of a couple key system libraries at install time (and does not
actually provide those libraries), preventing a number of things from working
properly, including apparently the rpm database.
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA/CoRA Division FAX: 303-415-9702
3380 Mitchell Lane [email protected]
Boulder, CO 80301 http://www.cora.nwra.com
_______________________________________________
users mailing list
[email protected]
http://lists.rpmforge.net/mailman/listinfo/users
