The below message shows, then the update proceeds to completion. Is it a problem? Is there something I should do or is it something at the repository side (which one?). I found articles suggested rebuilding the rpm db. However, since this problem happened on two machines I find it unusual to have the same issue in the two databases. [later] following a vague memory of looking into it before, I looked at an old package tux.x86_64 3.2.18-9.fc6 @System and then $ rpm -V tux.x86_64 error: Verifying a signature using certificate CAB44B996F27744E86127CDFB44269D04F2A6FD2 (Fedora Project <fedora@xxxxxxxxxx>): Key B44269D04F2A6FD2 invalid: not signing capable error: rpmdbNextIterator: skipping h# 61 Header V3 DSA/SHA1 Signature, key ID 4f2a6fd2: BAD Header SHA1 digest: OK package tux.x86_64 is not installed Is it related?? Why the error showing now? TIA ===== Running transaction check error: Verifying a signature using certificate CAB44B996F27744E86127CDFB44269D04F2A6FD2 (Fedora Project <fedora@xxxxxxxxxx>): Key B44269D04F2A6FD2 invalid: not signing capable error: rpmdbNextIterator: skipping h# 61 Header V3 DSA/SHA1 Signature, key ID 4f2a6fd2: BAD Header SHA1 digest: OK Transaction check succeeded. ===== -- Eyal Lebedinsky (fedora@xxxxxxxxxxxxxx) _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
