Description of problem:
I have chromium installed from http://repos.fedorapeople.org/repos/spot/chromium/. Note that packages in this repo aren't signed.
There's currently an update to chromium. If I try to do the update through apper, it pops up the "Installing unsigned packages" warning dialogue box. If I hit "Yes", it goes away and then immediately pops back up -- indefinitely, as far as I can tell.
Doing the same update through yum works fine, and doing the apper update with chromium un-checked also works.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Confirming. I have the same problem.
Still happening (I now have updates to unsigned texlive packages from http://jnovy.fedorapeople.org/texlive/)
Created attachment 577278 [details]
... and here's what seems to be the obvious patch to fix things. Untested as yet, but I'll try it out shortly.
Aha, it's actually been fixed in upstream git for about 10 days, with what looks like the same patch plus a bit more bookkeeping
apper-0.7.1-2.fc17 has been submitted as an update for Fedora 17.
apper-0.7.1-2.fc16 has been submitted as an update for Fedora 16.
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing apper-0.7.1-2.fc16'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
PackageKit-0.7.4-1.fc17, apper-0.7.1-4.fc17 has been submitted as an update for Fedora 17.
PackageKit-0.7.4-1.fc17, apper-0.7.1-4.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
apper-0.7.1-3.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.