Bug 620943 - Require selinux-policy to fix the update issue for new installs
Summary: Require selinux-policy to fix the update issue for new installs
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: PackageKit
Version: 13
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-03 20:02 UTC by Adel Gadllah
Modified: 2010-09-09 01:25 UTC (History)
4 users (show)

Fixed In Version: PackageKit-0.6.6-2.fc13
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-09-09 01:25:47 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Adel Gadllah 2010-08-03 20:02:52 UTC
Description of problem:

See https://fedorahosted.org/fesco/ticket/440#comment:23

Basically we need to make PackageKit require the fixed selinux-policy to get out of this.

Comment 1 Kevin Kofler 2010-08-09 22:14:57 UTC
> I am not sure how a conflict would solve that though. A "Requires: selinux-policy
> >= fixedVersion" would.

Conflicts: selinux-policy < fixedVersion
achieves the same thing without needlessly requiring selinux-policy.

Comment 2 Fedora Update System 2010-09-02 10:06:01 UTC
PackageKit-0.6.6-2.fc13 has been submitted as an update for Fedora 13.
https://admin.fedoraproject.org/updates/PackageKit-0.6.6-2.fc13

Comment 3 Fedora Update System 2010-09-02 20:35:48 UTC
PackageKit-0.6.6-2.fc13 has been pushed to the Fedora 13 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update PackageKit'.  You can provide feedback for this update here: https://admin.fedoraproject.org/updates/PackageKit-0.6.6-2.fc13

Comment 4 Fedora Update System 2010-09-09 01:25:42 UTC
PackageKit-0.6.6-2.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.


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