[SOLVED] Update fails in new Fedora 17 installation
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I recently installed Fedora 17 on a old HP/Pavilion laptop and receive an error when applying the first group of updates.
The error is thrown with:
Signature URL: /etc/pki/rpm-gpg/RPM-GPG-Key-fedora-i386
Signature user identifiers: Fedora 17 <email@example.com>
Signature identifier: 1ACA3465
The update process asks: "Do you recognize the user and trust this key?", and offers "Yes" or "Cancel".
If "Yes" is chosen, a dialog box appears with space to enter characters, but nothing I submit there works.
If "Cancel" is chosen, the update halts.
If I restart the update, it proceeds to the same point, with the same error and choices.
I have looked in /etc/pki/ and find there what appears to be the correct key.
I have found references on the Fedora site to a key change project. But, it refers to Fedora 8 and 9, not later distributions.
Open a terminal window and then run 'sudo yum -y update'. If Sudo isn't installed or configured then you probably want to install that first. Try 'su -l' if your unprivileged user account isn't in the wheel group or try to log in as root on another terminal.
Thank you, AwesomeMachine, JohnVV, lleb, and UnSpawn (in alphabetical order):
Since there was some conflict, I merged your comments giving attention to cautions expressed by two of you.
From my user account I ran: yum -h
I noticed the REPOLIST command, and then ran: yum -d3 -t repolist
The command returned: Error: Cannot retrieve metalink for repository: fedora. Please verify its path and try again
Thinking a database error might be at fault, I logged in as root and ran: yum -d3 -t clean all rpm --rebuilddb yum -d3 -t update
The update manager "built updates object", "set up package sacks", and then return the same error as above.
My newbie toes fell comfortable in the water, but any ideas on how I resolve the metalink problem?
Thank you, everyone...
The problem I experienced with not being able to install updates in a new installation of Fedora 17 is solved. All of your contributions were valuable and very much appreciated.