LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   Update fails in new Fedora 17 installation (https://www.linuxquestions.org/questions/linux-newbie-8/update-fails-in-new-fedora-17-installation-4175461217/)

1881Alex1099 05-08-2013 08:31 PM

Update fails in new Fedora 17 installation
 
Hello, everyone...
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 <fedora@fedoraproject.org>
Signature identifier: 1ACA3465
Package: libreoffice-core-1:3.7.2-12.fc17.i686
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.
Any ideas?

unSpawn 05-09-2013 02:13 AM

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.

John VV 05-09-2013 09:55 PM

and if you used the " pam hack" to allow root to login to the gui ( gnome and KDE )
that can cause problems like this

yum issues can also be caused by a "bad" rpm database
the very first thing to try is
Code:

su -
---- your root password when asked for ---
yum clean all
rpm --rebuilddb
yum update


lleb 05-10-2013 12:26 AM

yes what John VV stated, no need to install and configure sudo, that is not the best practice for handeling Linux. sorry unSpawn. sudo at times can be helpful, but this is not one of them.

updates and repairs to the OS should be properly handled only by root, not sudo.

unSpawn 05-10-2013 03:45 AM

Quote:

Originally Posted by John VV (Post 4948264)
the very first thing to try is

Actually the very first thing to do would be to look at the log file or else make the application show debug info telling you what is wrong, which running
Code:

yum -d3 update
would do.


Quote:

Originally Posted by lleb (Post 4948314)
updates and repairs to the OS should be properly handled only by root, not sudo.

Other than depsolves I've never had problems running 'sudo yum update' so that's a proven "no" wrt updates.

AwesomeMachine 05-10-2013 08:00 AM

Yum has a few ignore options. If you just type, yum, it will print the options

1881Alex1099 05-10-2013 05:38 PM

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?

1881Alex1099 05-10-2013 06:07 PM

Hello again, everyone:
I found the cause for the "metalink" problem was a bad Ethernet cable. I will report on progress later.

1881Alex1099 05-11-2013 12:25 PM

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.
Best regards...


All times are GMT -5. The time now is 01:47 AM.