Hide Forgot
Description of problem: dnf system-upgrade download --releasever=25 prompts for acceptance of rpmfusion keys but fails as the keys are not found. Version-Release number of selected component (if applicable): How reproducible: Everytime Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: Worked around the issue by going to the rpmfusion.org site and downloading the rpm files with the keys. Then had to for installation rpm -ivh --nodeps --nosignature <file> to get them to install on host. After they were installed did dnf system-upgrade download --refresh --releasever=25 and when prompted for acceptance of key it worked. I did not see where I could post a duplicate of this report in the rpmfusion reporting system.
Sounds like a bug (RFE) in the rpmfusion-nonfree-release-24 package. It should include the key for the next release so that people can upgrade seamlessly.
Hm, rpmfusion-nonfree-release-24 does have those keys. So I'm not sure why you wouldn't have them. Do you have rpmfusion-nonfree-release-24-2 installed? What keys exactly were missing?
I checked, prior to installing the rpmfusion rpm packages there were keys as you way for release 24 but not release 25. After installing there are keys for releases up to 27.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.