| Summary: | drakrpm-edit-media manage keys option shows all keys not found in keyring | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Dave Hodgins <davidwhodgins> |
| Component: | RPM Packages | Assignee: | Thierry Vignaud <thierry.vignaud> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | 3 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | rpmdrake-5.49-1.mga3.src.rpm | CVE: | |
| Status comment: | |||
|
Description
Dave Hodgins
2013-08-20 23:28:25 CEST
On my Mageia 3 x86-64, system when I select a Mageia repo in drakrpm-edit-media, Options - Manage Keys, the key is displayed along with its description: 80420f66 (Mageia Packages <packages@mageia.org>) I don't see any error message. Selecting Add, offers the option of either the Mageia key or the Google key. (This latter I had to import using rpm --import.) Both are displayed along with the relevant description. FWIW, I don't see any errors on my Cauldron system, either. The Mageia key is displayed correctly. (I don't have any third-party repo defined on that system.) Jim It's working in my vb installs too. Might be the difference is that the host system was upgraded from Mageia 2. The only difference I can see is the dates In the Mageia 3 x86_64 host system ... $ rpm -q -i gpg-pubkey-80420f66-4d4fe123|grep Date Install Date: 2013-01-12T14:59:50 EST Build Date : 2013-01-12T14:59:50 EST In the Mageia 3 x86_64 vb guest system ... $ rpm -q -i gpg-pubkey-80420f66-4d4fe123|grep Date Install Date: Fri 24 May 2013 07:47:34 PM EDT Build Date : Mon 07 Feb 2011 07:10:11 AM EST I suspect I had manually added the key using rpm --import, but am not positive. In the guest, where it works, I don't see anything related to the key in /var/lib/urpmi, so don't know what difference it might make, using rpm --import. I'll dig into this more later, to see if I can figure out what the difference is between the two systems. Mageia 3 changed to end-of-life (EOL) status 4 months ago. http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad Status:
NEW =>
RESOLVED |