Bug 17299 - Demon reports incorrect packages for updating
Summary: Demon reports incorrect packages for updating
Alias: None
Product: PackageKit
Classification: Unclassified
Component: backend-yum (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Richard Hughes
QA Contact:
Depends on:
Reported: 2008-08-25 17:41 UTC by Aidan Skinner
Modified: 2008-08-26 01:01 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Description Aidan Skinner 2008-08-25 17:41:07 UTC
This is with packagekit head:

[root@contemplation src]# yum update
Loaded plugins: refresh-packagekit
livna                                                    | 2.1 kB     00:00     
freemind                                                 |  951 B     00:00     
fedora                                                   | 2.4 kB     00:00     
rpm-based-noarch                                         | 1.1 kB     00:00     
rpm-based                                                | 1.1 kB     00:00     
updates                                                  | 2.3 kB     00:00     
Setting up Update Process
No Packages marked for Update

aidan@contemplation:~/hacking/rum[ruck]/src$ ./rum lu (<-- this calls GetUpdates)

Repository | Name     | Version                  
fedora     | gtkhtml2 | 2.19.1-4.fc8             
installed  | kernel   | 2.6.23-0.115.rc3.git1.fc8
fedora     | powertop | 1.8-1.fc8                

I have no idea why it's pulling in fc8 packages...
Comment 1 Richard Hughes 2008-08-26 01:01:03 UTC
It looks like you are running with the dummy backend, not the yum backend. Note: if you start PackageKit using "sudo ./run-pk.sh" then by default the dummy backend is started. You need to use "sudo ./run-pk.sh yum" to start a specific backend, or start packagekitd with no arguments, and then the config file is used. Look in backends/dummy/pk-backend-dummy.c for those F8 packages :-)

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.