Bug 29335

Summary: PackageKit displaying multiple versions of the same package
Product: PackageKit Reporter: Jens Knutson <jens.knutson>
Component: GeneralAssignee: Richard Hughes <richard>
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: All   
OS: All   
i915 platform: i915 features:
Attachments: Searching for packages starting with 'libvirt', using pkcon
Searching for packages starting with 'libvirt', using yum
'pkmon -v' output

Description Jens Knutson 2010-07-31 18:35:46 UTC
When searching for packages with gnome-packagekit or pkcon, I get dupelicate packages.

It looks like it's displaying the version in the base repo, and then the current package in the updates repo.

Here's all the required bits:

jensck@Forge $ packagekit-bugreport.sh 
Distro version:       Fedora release 13 (Goddard)
PackageKit version:   0.6.6
PackageKit Process Information:
root     14355  0.0  0.1  77312  4544 ?        S    20:05   0:00 /usr/libexec/packagekitd

jensck@Forge $ rpm -q gnome-packagekit 

I have attached examples, compared to the output of "yum list <package>", as well as the output of pkmon -v, which I hope is what you intend as the packagekitd trace...
Comment 1 Jens Knutson 2010-07-31 18:37:17 UTC
Created attachment 37490 [details]
Searching for packages starting with 'libvirt', using pkcon
Comment 2 Jens Knutson 2010-07-31 18:37:39 UTC
Created attachment 37491 [details]
Searching for packages starting with 'libvirt', using yum
Comment 3 Jens Knutson 2010-07-31 18:38:18 UTC
Created attachment 37492 [details]
'pkmon -v' output
Comment 4 Jean-Fran├žois Fortin Tam 2012-01-05 11:04:10 UTC
Hi there,
This bug report is very old and based on a version not supported anymore. By upgrading to a newer version of PackageKit you could receive bug fixes and new functionality. You may need to upgrade your Linux distribution to obtain a newer version of PackageKit.
Please feel free to reopen this bug if the problem still occurs with the latest version.

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.