Bug 601594 - Unsigned updates can't be installed
Summary: Unsigned updates can't be installed
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kpackagekit
Version: 14
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Steven M. Parrish
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-08 09:44 UTC by Martin Kho
Modified: 2010-09-14 12:34 UTC (History)
6 users (show)

Fixed In Version: 0.6.1
Clone Of:
Environment:
Last Closed: 2010-09-14 12:34:46 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Martin Kho 2010-06-08 09:44:31 UTC
Description of problem:
In rawhide it's not uncommon that updates are not signed. kpackagekit won't let the user install them. Authentication missing?

Version-Release number of selected component (if applicable):
kpackagekit-0.6.0-2.fc13.x86_64
PackageKit-0.6.5-1.fc14.x86_64

Steps to Reproduce:
1. Select updates and press Apply button (a command board appears in the systray stating: "An untrusted package is installed. The package <package name> from rawhide is untrusted")
2. Press Continue button in the additional packages dialog (a message appears stating: "You are about to install unsigned packages can compromise your system, as it is impossible to verify if the software came from a trusted source. Are you sure you want to continue installation?")
3. Press Yes-button (a dialog appears stating that kpackagekit is "Waiting for service to start") The service (?) will never start.
  
Actual results:
Unsigned packages can't be installed

Expected results:
Unsigned packages can be installed (after authentication?)

Additional info:

Comment 1 Bug Zapper 2010-07-30 12:03:59 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle.
Changing version to '14'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Martin Kho 2010-09-08 19:37:14 UTC
Hi,

kpackagekit 0.6.1 solves this issue. I suppose that this report can be closed.

Thanks for the nice work! It seems that kpackagekit is on it's way back :-)

Martin Kho


Note You need to log in before you can comment on or make changes to this bug.