On 01/27/2012 10:21 AM, Reindl Harald wrote: yum clean all and yum upgrade will solve some problems, but certainly not 99% of them. For example, I *am* a tester of rawhide and have been fighting a battle with the x11 updates. I finally removed about 25 x11 packages that I determined weren't necessary on my system, ran the yum update, and finally was able to get my x11 updated. yum clean all would not have done *anything* to correct that issue.Am 27.01.2012 17:14, schrieb Kevin Martin:On 01/27/2012 09:56 AM, Reindl Harald wrote:Am 27.01.2012 16:15, schrieb Kevin Martin:On 01/27/2012 08:51 AM, Reindl Harald wrote:Am 27.01.2012 15:34, schrieb Kaushik Guha:Dear Friends, While upgrading through "Yumex" ,everything is running well,except a problem is occurring while upgrading packages. 19:46:52 : YUM: warning: rpmts_HdrFromFdno: Header V3 RSA/SHA256 Signature, key ID 8296fa0f: NOKEY /19:46:52 : ERROR: Error in yum Transaction : Public key for npapi-vlc-1.2.0-0.3gitf568362.fc17.x86_64.rpm is not installed/ How to rectify the error in yum Transaction,on the last line.Please Help me.this package must not be in the F16 repo and i guess this is already fixed throw away yumex and type "yum cleanall && yum upgrade" in a root-shell if you do not want to waitInstall the public key or turn on "no GPG check" under options in Yumex. Kevinwhy in the world do you give such TOTALLY WRONG advises after a correct answer? a) .fc17 is not intented to be for F16 b) "noGPG check" generally to set is a dumb actionOh, and by the way, it's "advice", not advises, and your "correct answer" was not necessarily correct at all, just your shooting your mouth off without doing any actual research as to what may have occurred. If you can't offer semi-knowledgeable advice, don't attack people who do."yum clean all && yum upgrade" wil solve 99 out of 100 dependecnie/repo-problems if you do not want to use a shell wait until it goes away over the time the third option is make a bugreport that the repo needs to be fixed tell someone he should disable gpgcheck is dumb, because you suggest if people have problems they should do this - WTF do you understand why this exists and what damage are hapenning if you get a bad core-package on your system which was only installed because you disabled gpgcheck? And yes, I'm well aware of what the gpgchecking does and why it should not be disabled. However, being able to disable it is there for a reason and he was trying to update a package from a repository that he knows and, presumably, trusts. And sometimes the gpg keys aren't available or are screwed up. Kevin |
-- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org