Bug 806508

Summary: "Unsigned packages" popup constantly reappears
Product: [Fedora] Fedora Reporter: Mary Ellen Foster <mefoster>
Component: apperAssignee: Rex Dieter <rdieter>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: atorkhov, hughsient, kevin, ltinkl, rdieter, smparrish
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: apper-0.7.1-3.fc16 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-05-02 04:41:05 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Proposed patch none

Description Mary Ellen Foster 2012-03-24 10:01:11 UTC 
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):
apper-0.7.1-1.fc16.x86_64

How reproducible:
Every time

Steps to Reproduce:
(see above)
Comment 1 Alexey Torkhov 2012-03-28 19:25:53 UTC 
Confirming. I have the same problem.
Comment 2 Mary Ellen Foster 2012-04-13 09:05:57 UTC 
Still happening (I now have updates to unsigned texlive packages from http://jnovy.fedorapeople.org/texlive/)
Comment 3 Mary Ellen Foster 2012-04-13 09:17:11 UTC 
Created attachment 577278 [details]
Proposed patch

... and here's what seems to be the obvious patch to fix things. Untested as yet, but I'll try it out shortly.
Comment 4 Mary Ellen Foster 2012-04-13 09:19:47 UTC 
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
Comment 5 Fedora Update System 2012-04-16 21:31:24 UTC 
apper-0.7.1-2.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/apper-0.7.1-2.fc17
Comment 6 Fedora Update System 2012-04-16 21:32:24 UTC 
apper-0.7.1-2.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/apper-0.7.1-2.fc16
Comment 7 Fedora Update System 2012-04-18 19:31:54 UTC 
Package apper-0.7.1-2.fc16:
* 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:
https://admin.fedoraproject.org/updates/FEDORA-2012-6029/apper-0.7.1-2.fc16
then log in and leave karma (feedback).
Comment 8 Fedora Update System 2012-04-26 12:32:45 UTC 
PackageKit-0.7.4-1.fc17, apper-0.7.1-4.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/FEDORA-2012-6580/apper-0.7.1-4.fc17,PackageKit-0.7.4-1.fc17
Comment 9 Fedora Update System 2012-05-02 04:41:05 UTC 
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.
Comment 10 Fedora Update System 2012-05-03 22:50:32 UTC 
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.