Re: fedup failure [SOLVED]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 23 March 2014 23:13, Greg Woods <woods@xxxxxxxx> wrote:
On Sun, 2014-03-23 at 17:19 +0200, Ahmad Samir wrote:

>         Downloading failed: GPG key retrieval failed: [Errno 14]
>         curl#37 -
>         "Couldn't open
>         file /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-x86_64"

>
> Have a look at:
> https://bugzilla.redhat.com/show_bug.cgi?id=1044086#c11

Thank you for the pointer, that worked. I had to run "rpmkeys --import"
manually. (I went ahead and did the rpmfusion keys too while I was at
it). I guess that's a bug, since I have never had to do this before, the
package management system has always prompted me automatically to import
keys as long as it could find them in a /etc/pki/rpm-gpg file. But
manually doing the imports worked, fedup is now chugging along after the
System-Upgrade reboot.


The other link I posted[1] is about the gpgkey entry in fedora .repo files in /etc/yum.repos.d/*.repo; IIUC at some point it was changed to be:
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$releasever-$basearch

note the $releasever bit there; the error message you posted mentioned:
/etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-x86_64

The point is you'd modified one of the .repo files manually, then when the fedora-release package was updated your changes would have been kept and then new .repo file the updated package would have been installed as *.repo.rpmnew; so you'd better check that issue to prevent similar problems in the future...

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1003091

 
It was a bit annoying, since this happened right after I discovered that
upgrading via the DVD is no longer an option, we're supposed to use
fedup, then fedup didn't work.

As Patrick O'Callaghan posted, it is still an option, as in fedup could use the non-live DVD ISO to upgrade: http://fedoraproject.org/wiki/FedUp#ISO_File
(I've never used fedup so I have no idea how well using the ISO to upgrade works).
 
I should have thought of searching the
bugzilla to see if this had already been reported.

--Greg



--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org



--
Ahmad Samir
-- 
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux