Up2Date Error

BBCore · #1 26th April 2005, 01:58 PM

Hey what's

I just left Ubuntu based on performance and also to many bugs for me to handle at the moment, but I want to try and find out why I can't get ALL the packages to show up in the up2date app. It shows 45 updates available but 9 of those are not wanting to update when I check them off for the update to go through.

It's been happening since last night, so I am still not sure what I need to do in order to get the new update for the up2date app which is the 4.4..15-4. It also says I cannot update any other packages until the new version of up2date is installed.

Any Ideas?

AndyGreen · #2 26th April 2005, 02:05 PM

Why not give yum a spin instead. Fire up a root console.

If it is your first run of yum, you may need to give rpm the Fedora key (it'll tell you if so)

rpm --import /usr/share/doc/fedora-release-3/RPM-GPG-KEY-fedora

then

yum update

BBCore · #3 26th April 2005, 02:24 PM

Quote:

Originally Posted by AndyGreen

Why not give yum a spin instead. Fire up a root console.

If it is your first run of yum, you may need to give rpm the Fedora key (it'll tell you if so)

rpm --import /usr/share/doc/fedora-release-3/RPM-GPG-KEY-fedora

then

yum update

Cool, the update was fine, but it needs the GPG Key, in which I get the following error:

[***@localhost usr]# rpm --import /usr/share/doc/fedora-release-3/RPM-GPG-KEY-fedora
error: /usr/share/doc/fedora-release-3/RPM-GPG-KEY-fedora: import read failed(-1).

AndyGreen · #4 26th April 2005, 02:29 PM

You are on FC3, right?

Try this instead

rpm --import http://fedora.redhat.com/about/security/4F2A6FD2.txt

BBCore · #5 26th April 2005, 02:41 PM

Quote:

Originally Posted by AndyGreen

You are on FC3, right?

Try this instead

rpm --import http://fedora.redhat.com/about/security/4F2A6FD2.txt

Sorry I should've told you before, I'm on FC4 Test.

My Apologies

Edit: ok got the update to work, just need the GPG to sign the repo's.

AndyGreen · #6 26th April 2005, 02:43 PM

Well you can still use yum, just the path to the key on your machine is different is all, which is why it failed. Use the second method.

BBCore · #7 26th April 2005, 02:47 PM

Ok, I did the second method, and it worked, where would this key goto, and how do I set the path to it?

Sorry I am very new to Fedora compared to Ubuntu

AndyGreen · #8 26th April 2005, 02:49 PM

The key step is done -- RPM imported it and now knows how to check package signatures to see if they really came from Fedora. Now you are ready to just try

yum update

BBCore · #9 26th April 2005, 02:52 PM

Quote:

Originally Posted by AndyGreen

The key step is done -- RPM imported it and now knows how to check package signatures to see if they really came from Fedora. Now you are ready to just try

yum update

Good deal

sorry if I am rushing to fast, and about the hassle, trying to get this fixed before heading off to work.

Just a quick note, I got this error when trying to do yum update

unsigned package gnome-utils-2.10.0-2.i386.rpm, I'm thinking it might do that with all of them...

AndyGreen · #10 26th April 2005, 02:55 PM

Yep -- you need the development key since you are on the development branch of Fedora and getting development packages signed with the development key.

rpm --import http://fedora.redhat.com/about/security/1CDDBCA9.txt

BBCore · #11 26th April 2005, 03:00 PM

Quote:

Originally Posted by AndyGreen

Yep -- you need the development key since you are on the development branch of Fedora and getting development packages signed with the development key.

rpm --import http://fedora.redhat.com/about/security/1CDDBCA9.txt

Yea, it's stil not working, keep getting this error when doing the hands on the up2date tool.

The package kernel-2.6.11-1.1267_FC4 is not signed with a GPG signature. Continue?

Not sure what to do at this point seems like a bug to me....

AndyGreen · #12 26th April 2005, 03:03 PM

Not a bug. Some of the development packages -- hey, you notice all the difficulties you are having are all to do with your being on development branch? -- are unsigned. By default yum insists to have a signature before accepting the file. You can turn this off by editing

/etc/yum.conf

and changing

gpgcheck=1

to

gpgcheck=0

You may also need to look inside

/etc/yum.repos.d/

and do the same gpgcheck=0 job to the .repo file in there corresponding to the development repo.

BBCore · #13 26th April 2005, 03:21 PM

Worked like a charm!

Thank You Andy!, I really appreciate your help on this my friend, very much appreciated!!

Have a great day

TheCat · #14 22nd June 2005, 10:54 PM

I'm using the release version of Fedora Core 4, and Up2Date is constantly prompting me for packages, e.g.

The package xorg-x11-xfs-6.8.2-37 is not signed with a GPG signature. Continue?

Note that I'm not using any development packages - the only modification I've made to my yum configuration file is adding livna. Why aren't these release packages signed?

BBCore · #15 24th June 2005, 03:21 AM

Quote:

Originally Posted by TheCat

I'm using the release version of Fedora Core 4, and Up2Date is constantly prompting me for packages, e.g.

The package xorg-x11-xfs-6.8.2-37 is not signed with a GPG signature. Continue?

Note that I'm not using any development packages - the only modification I've made to my yum configuration file is adding livna. Why aren't these release packages signed?

Hmm, I see what you mean, but I am not exactly sure...