Description of problem:
PackageKit-Qt is pretty useless without PackageKit. It should require it.
Version-Release number of selected component (if applicable):
PackageKit-Qt-0.8.9-2.fc20 has been submitted as an update for Fedora 20.
PackageKit-Qt-0.8.9-2.fc19 has been submitted as an update for Fedora 19.
Fixed in F21 and Rawhide, updates in for F19 and F20.
Tested PackageKit-Qt-0.8.9-2.fc20,the requires for PackageKit is added
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing PackageKit-Qt-0.8.9-2.fc19'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
PackageKit-Qt-0.9.2-6.fc21 has been submitted as an update for Fedora 21.
Proposed as a Freeze Exception for 21-alpha by Fedora user rdieter using the blocker tracking app because:
installing updates via apper on kde spin is currently non-functional (or we can just punt and make it a f21-beta blocker, but since we have the easyfix now...)
PackageKit-Qt-0.8.9-2.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
Reopening as we have to be sure this hits Beta. Adding CommonBugs for Alpha.
Proposed as a Blocker for 21-beta by Fedora user jreznik using the blocker tracking app because:
Breaks Beta criterion: "The installed system must be able to download and install updates with the default graphical package manager in all release-blocking desktops." and "Release-blocking desktops must notify the user of available updates, but must not do so when running as a live image." as it fails without PackageKit being not available.
Wait, we DIDN'T pull this into Alpha? WTF? WTF do we even have a freeze exception process for? Rex requested the freeze exception 6 days ago, the update was already queued for stable at that time, why TF did it not get pulled into the RC?
Also, working around this in the spin kickstart would have been a 1-line change, if people had just told us that they were not going to pull the fixed package in.
IMHO, Alpha RC1 needs to be a no-go, and we need to pull in this fix and the updated KDE kickstart (size fix, hoping the restoral of PackageKit won't readd too much size) for a new RC. I understand that neither is technically a blocker for Alpha, but at least this issue was filed as a freeze exception well in time, it's not our fault that it has not been processed! (And by the way, I don't understand why working updates are not required for Alpha to begin with.)
For Alpha, working updates are required but with yum: "The installed system must be able to download and install updates with the default console package manager."
I'd say if we would have to respin, it could be included but we will try to minimize changes between composes and as this is not Alpha blocker, no promises at all.
"Rex requested the freeze exception 6 days ago, the update was already queued for stable at that time, why TF did it not get pulled into the RC?"
Because the bug got closed by the F20 update push - see c#8. I marked the F20 update as fixing this bug, so the bug got closed when that went stable, and obviously F20 update pushes aren't blocked by the F21 freeze.
Since the bug was closed, it dropped off the FE list and wasn't reviewed at the meetings.
I'm sorry for the mess, it's my fault :( I think when I first sent the F21 build I thought Bodhi hadn't yet been activated so I didn't need to create an update, and also I didn't realize this bug was so important - I thought it just meant you could inadvertently remove PackageKit manually, I didn't realize it was keeping it off the lives. My apologies.
PackageKit-Qt-0.9.2-6.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
PackageKit-Qt-0.8.9-2.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.