On Sat, 2006-02-25 at 19:39 +1000, david walcroft wrote: > Craig White wrote: > > On Sat, 2006-02-25 at 13:17 +1000, david walcroft wrote: > > > >>Paul Howarth wrote: > >> > >>>On Fri, 2006-02-24 at 16:47 +1000, david walcroft wrote: > >>> > >>> > >>>>How do I handle unsigned rpm's,I've got two holding up 645M of updates. > >>>>Pango and libpixman, [FC 4] > >>> > >>> > >>>Some of the FC4 release packages were signed with the wrong key. Yum > >>>erroneous reports that they're unsigned. > >>> > >>># rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY > >>> > >>>will probably fix it if that's what's happening here. > >>> > >>>Paul. > >>> > >> > >>Sorry Paul but it didn't,I already had that GPGkey installed,most of > >>those rpm's are from the 'nrpms repo'and I cannot find its GPG key.Is > >>there a central point where all keys url's are kept or available. > >> > > > > ---- > > what is nrpms repo? > > > > whatever nrpms repo is, you can probably turn off checking for that repo > > only... > > > > # cat /etc/yum.repos.d/rpmforge.repo > > # Name: RPMforge RPM Repository for Fedora Core 4 - i386 > > # URL: http://rpmforge.net/ > > [rpmforge] > > name = Fedora Core 4 - i386 - RPMforge.net - dries > > #baseurl = http://apt.sw.be/dries/fedora/fc4/$basearch/dries/RPMS > > mirrorlist = http://apt.sw.be/dries/fedora/fc4/mirrors-rpmforge > > #mirrorlist = file:///etc/yum.repos.d/mirrors-rpmforge > > #exclude=xine xine-lib xine-skins > > enabled = 1 > > gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rpmforge-dries > > gpgcheck = 1 > > > > (if I change gpgcheck = 1 to gpgcheck = 0, then it doesn't do a gpg > > check for rpm's from that repo) > > > > Craig > > > Well here's what happened Craig,after changing to gpgcheck=0, > > Install 12 Package(s) > Update 295 Package(s) > Remove 0 Package(s) > Total download size: 622 M > Downloading Packages: > Running Transaction Test > [david@reddwarf ~]$ > > As you see it either crashed or decided nothing is to be done,I favour a > crash. No packages where downloaded. ---- am I to assume that you are executing this with a sudo command? Try doing an 'su -' and then running the command rather than sudo as there may be more information that is output in the shell that is supressed in a sudo command. You also might want to add '-e 1' to your yum command to get a report of any/all errors Craig Craig
