Bug 628114
Summary: | Manual confirmation of signature leads to error | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | tim <tim> |
Component: | PackageKit | Assignee: | Richard Hughes <rhughes> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | low | ||
Version: | 13 | CC: | jonathan, rhughes, sangu.fedora, smparrish |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-09-23 08:34:23 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
tim
2010-08-28 00:27:44 UTC
Maybe I should note that I installed Fedora 13 from a LinuxFormat (magazine) disk and I installed all updates I could find. This happened shortly after the reboot that was needed for the updates. The problem can be worked around by manually installing the rpmfusion signature using a download from it's website and installing it using su -c 'rpm --import RPM-GPG-KEY-rpmfusion-free-fedora-13' But this is only a way to work around the problem found here. Maybe there are actually two problems at work here: 1. The rpmfusion repo doesn't install correctly from it's RPM, because the key is not correctly imported. (whether this is a problem with the rpmfusion rpm or with the install functionality is a subject for an other discussion, I'd say. It's not within my power to analyse this to know for sure.) 2. Using the PackageKit UI to confirm that the key is to be trusted, does not work because of the above mentioned error log. (I don't know enough python and don't know enough about fedora's inner workings to figure this one out though..) *** This bug has been marked as a duplicate of bug 622179 *** |