Bug 440427

Summary: pkcon is acting odd
Product: [Fedora] Fedora Reporter: Rahul Sundaram <sundaram>
Component: PackageKitAssignee: Robin Norwood <robin.norwood>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: rawhideCC: smohan
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-04-04 09:46:19 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Rahul Sundaram 2008-04-03 14:37:49 UTC
Description of problem:

# rpm -q PackageKit

PackageKit-0.1.11-0.620.20080401git.fc9.hughsie.i386

#  rpm -q PackageKit-cron
package PackageKit-cron is not installed

# pkcon install PackageKit-cron

resolve runtime was 3.0 seconds
    [=======================...................................]   40%          
Error: internal-error : Error in Package Signatures
P
a
c
k
a
g
e
 
P
a
c
k
a
g
e
K
i
t
-
c
r
o
n
-
0
.
1
.
1
1
-
0
.
6
3
0
.
2
0
0
8
0
4
0
2
g
i
t
.
f
c
9
.
h
u
g
h
s
i
e
.
i
3
8
6
.
r
p
m
 
i
s
 
n
o
t
 
s
i
g
n
e
d
install-package runtime was 12.1 seconds    

# rpm -q PackageKit-cron
package PackageKit-cron is not installed

Comment 1 Rahul Sundaram 2008-04-03 14:41:15 UTC
Just found out that, this is because package has not been signed. Yum correctly
deals with this. 

Comment 2 Richard Hughes 2008-04-03 16:14:57 UTC
Hmm. Do you get the one char on each line error with git?

Comment 3 Rahul Sundaram 2008-04-03 16:21:41 UTC
Yeah. This is what I got now

# rpm -q PackageKit
PackageKit-0.1.11-0.630.20080402git.fc9.hughsie.i386

To reproduce, enable gpg check on your repository and try to install any package
from that. Yum will fail noting that the package you are trying to install is
not signed. pkcon acts very odd. 

Comment 4 Tim Lauridsen 2008-04-04 09:46:19 UTC
i have fixed the one char at a line message, but the error is right.
you are adding gpgcheck to a repo with unsigned packages, then it shall fail.

yum will fail with the same error.