Hide Forgot
I have installed the SpiderOak ONE RPM. While on Fedora 24 this presented no problems on 25 I then get an error when running apper "check for updates": "The package that is being modified was not found on your system or in any software origin" This is a bit obscure. The details window gives: Curl error (37): Couldn't read a file:// file for file:///etc/pki/rpm-gpg/RPM-GPG-KEY-spideroak-2011;file:///etc/pki/rpm-gpg/RPM-GPG-KEY-spideroak-2015 [Couldn't open file /etc/pki/rpm-gpg/RPM-GPG-KEY-spideroak-2011;file:///etc/pki/rpm-gpg/RPM-GPG-KEY-spideroak-2015] The SpiderOak rpm repo has [spideroak-one-stable] name=SpiderOakONE Stable Distribution baseurl=http://apt.spideroak.com/spideroak_one_rpm/stable enabled=1 gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-spideroak-2011 file:///etc/pki/rpm-gpg/RPM-GPG-KEY-spideroak-2015 enablegroups=0 Interestingly running "dnf update --refresh" does not show any issue. I have tested this on a fresh F25 KDE ISO installed to a VM.
I wasn't even aware that including multiple keys via gpgkey= was possible, interesting.
Confirmed here, https://linux.die.net/man/5/yum.conf gpgkey A URL pointing to the ASCII-armored GPG key file for the repository. This option is used if yum needs a public key to verify a package and the required key hasn't been imported into the RPM database. If this option is set, yum will automatically import the key from the specified URL. You will be prompted before the key is installed unless the assumeyes option is set. Multiple URLs may be specified here in the same manner as the baseurl option (above). If a GPG key is required to install a package from a repository, all keys specified for that repository will be installed.
@Rex - this worked in F24 and somehow broke in F25.
Ah, sorry, I missed that detail. thanks.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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 Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.