Description of problem: If you look at bug 1214150, fedup can't currently upgrade system from F20 to F22, because there are no F22 gpg keys installed in F20 and the verification fails. Currently: [root@localhost ~]# ll /etc/pki/rpm-gpg/ total 16 lrwxrwxrwx. 1 root root 29 May 11 07:56 RPM-GPG-KEY-20-fedora -> RPM-GPG-KEY-fedora-20-primary lrwxrwxrwx. 1 root root 31 May 11 07:56 RPM-GPG-KEY-fedora-20-aarch64 -> RPM-GPG-KEY-fedora-20-secondary lrwxrwxrwx. 1 root root 29 May 11 07:56 RPM-GPG-KEY-fedora-20-armhfp -> RPM-GPG-KEY-fedora-20-primary lrwxrwxrwx. 1 root root 29 May 11 07:56 RPM-GPG-KEY-fedora-20-i386 -> RPM-GPG-KEY-fedora-20-primary lrwxrwxrwx. 1 root root 31 May 11 07:56 RPM-GPG-KEY-fedora-20-ppc -> RPM-GPG-KEY-fedora-20-secondary lrwxrwxrwx. 1 root root 31 May 11 07:56 RPM-GPG-KEY-fedora-20-ppc64 -> RPM-GPG-KEY-fedora-20-secondary -rw-r--r--. 1 root root 1658 Feb 19 2014 RPM-GPG-KEY-fedora-20-primary lrwxrwxrwx. 1 root root 31 May 11 07:56 RPM-GPG-KEY-fedora-20-s390 -> RPM-GPG-KEY-fedora-20-secondary lrwxrwxrwx. 1 root root 31 May 11 07:56 RPM-GPG-KEY-fedora-20-s390x -> RPM-GPG-KEY-fedora-20-secondary -rw-r--r--. 1 root root 3819 Feb 19 2014 RPM-GPG-KEY-fedora-20-secondary lrwxrwxrwx. 1 root root 29 May 11 07:56 RPM-GPG-KEY-fedora-20-x86_64 -> RPM-GPG-KEY-fedora-20-primary lrwxrwxrwx. 1 root root 31 May 11 07:56 RPM-GPG-KEY-fedora-21-aarch64 -> RPM-GPG-KEY-fedora-21-secondary lrwxrwxrwx. 1 root root 29 May 11 07:56 RPM-GPG-KEY-fedora-21-armhfp -> RPM-GPG-KEY-fedora-21-primary lrwxrwxrwx. 1 root root 29 May 11 07:56 RPM-GPG-KEY-fedora-21-i386 -> RPM-GPG-KEY-fedora-21-primary lrwxrwxrwx. 1 root root 31 May 11 07:56 RPM-GPG-KEY-fedora-21-ppc -> RPM-GPG-KEY-fedora-21-secondary lrwxrwxrwx. 1 root root 31 May 11 07:56 RPM-GPG-KEY-fedora-21-ppc64 -> RPM-GPG-KEY-fedora-21-secondary -rw-r--r--. 1 root root 1658 Feb 19 2014 RPM-GPG-KEY-fedora-21-primary lrwxrwxrwx. 1 root root 31 May 11 07:56 RPM-GPG-KEY-fedora-21-s390 -> RPM-GPG-KEY-fedora-21-secondary lrwxrwxrwx. 1 root root 31 May 11 07:56 RPM-GPG-KEY-fedora-21-s390x -> RPM-GPG-KEY-fedora-21-secondary -rw-r--r--. 1 root root 3819 Feb 19 2014 RPM-GPG-KEY-fedora-21-secondary lrwxrwxrwx. 1 root root 29 May 11 07:56 RPM-GPG-KEY-fedora-21-x86_64 -> RPM-GPG-KEY-fedora-21-primary Will Woods claims the correct solution is to include F22 in F20. Please do so, thank you. Version-Release number of selected component (if applicable): fedora-release-20-3.noarch
iscussed at the 2015-05-11 blocker review meeting[0]. Voted as RejectedFreezeException. AGREED: 1220358 - RejectedFreezeException - as the issue here is in F20, there's no reason to mark it as an FE for F22. (adamw, 17:57:25) [0]: http://meetbot.fedoraproject.org/fedora-blocker-review/2015-05-11/
fedora-release-20-4 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/fedora-release-20-4
Package fedora-release-20-4: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing fedora-release-20-4' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-8268/fedora-release-20-4 then log in and leave karma (feedback).
fedora-release-20-4 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
Still broken, even with 20-4. Looks like it's trying to import a key with no extension. I simply imported the x86_64 key for F22 from /etc/pki/ Seems to have worked - after also importing the rpmfusion keys, everything looks ok after completion.