Description of problem:
wpa_supplicant RPM not signed.
Although of little interest in itself, problem causes yum update to abort
without doing anything.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. yum update wpa_supplicant
# yum update wpa_supplicant
Loading "refresh-updatesd" plugin
Setting up Update Process
--> Running transaction check
---> Package wpa_supplicant.i386 1:0.5.7-12.fc8 set to be updated
--> Finished Dependency Resolution
Package Arch Version Repository Size
wpa_supplicant i386 1:0.5.7-12.fc8 fedora 253 k
Install 0 Package(s)
Update 1 Package(s)
Remove 0 Package(s)
Total download size: 253 k
Is this ok [y/N]: y
Package wpa_supplicant-0.5.7-12.fc8.i386.rpm is not signed
Download and update of RPM
yum makes no attempt to update packages which do not depend on failed RPM.
This is something for yum developers to consider.
Pre-release packages are not signed. We made a mistake in changing the default
repositories from 'development' to 'fedora' and 'updates' (which require signed
packages) before the final F8 package set was ready.
Once F8 is completed we will sign the packages for the final release and this
problem will go away.
Until that happens, either:
1) Switch back to using the 'development' repo and disable 'fedora' and 'updates'
2) Disable gpg checking on the 'fedora' repo.
*** Bug 355361 has been marked as a duplicate of this bug. ***
*** Bug 355341 has been marked as a duplicate of this bug. ***
*** Bug 355311 has been marked as a duplicate of this bug. ***
*** Bug 355301 has been marked as a duplicate of this bug. ***
*** Bug 355181 has been marked as a duplicate of this bug. ***
You have marked various other bugs which I have submitted as duplicates of this.
I am not convinced of this because some of them were run with --nogpgcheck
or else the presence of --nogpgcheck made no difference.
I have been able to overcome the no signature problem with --nogpgcheck and I
believe there is a different problem with the installation of e.g. ginac and
There is evidence of this in the log files attached to the other (discarded)
I will not submit any further such reports - I will monitor what comes of it.
Created attachment 240581 [details]
rubygems fails with --nogpgcheck
I'd suggest changing the repository files (as discussed in comment #1) and then
yum clean all
it looks like you might have gotten some bad/mixed up metadata or
hope that helps.
Selected develpment repo and cleaned out metadata, now ok.
*** Bug 358521 has been marked as a duplicate of this bug. ***
All packages in rawhide should be signed now leading up to the F8 release.