Installed Software Partly Displayed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
packagekit (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Maverick |
Fix Released
|
Undecided
|
Unassigned | ||
Natty |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: kpackagekit
Kubuntu 10.10, KDE 4.5.4
kpackagekit:
Installed: 0.6.2-0ubuntu1
Candidate: 0.6.2-0ubuntu1
Version table:
*** 0.6.2-0ubuntu1 0
500 http://
100 /var/lib/
KPackageKit displays installed software in alphabetical order up to (not including) a certain item, presently a piece of software named 'homebank':
homebank:
Installed: 3.33
Candidate: 3.33
Package pin: 3.33
Version table:
4.2.1-1 1001
500 http://
*** 3.33 1001
100 /var/lib/
All software packages alphabetically following this homebank package are not displayed.
I used to hold the version of this homebank software as it is a third-party software that was in conflict with another official homebank software available through the Ubuntu repository, and I did not want to have this piece of software upgraded. I hold the version of this software package by adding the following lines to /etc/apt/
> more /etc/apt/
Package: homebank
Pin: version 3.33
Pin-Priority: 1001
Also, as you can see in the herewith enclosed dump of all installed software (dkpg -l), KPackageKit displays all installed software up to this homebank software put on hold ('hi' is displayed in front of the homebank software package, instead of 'ii'). I think this KPackageKit software bug is closely related to this hold operation.
By the way, there is no GUI in KpackageKit to hold the version of a specific software package and to prevent this software from being updated, e.g. because we are glad with the present version and we don't want to see any regression because of a new software update, or (as it is the case presently) because the package name of a third-party software conflicts with another 'official' package name.
Hope all these information would be helpful for identifying and fixing this bug in KPackageKit. I am available if you need any further information, or for testing a patch before an official delivery.
affects: | kpackagekit (Ubuntu) → packagekit (Ubuntu) |
Changed in packagekit (Ubuntu Natty): | |
status: | New → Fix Released |
tags: |
added: verification-done removed: verification-needed |
I could not reproduce your issue, but this might be related to a bug fixed in packagekit- backend- aptcc version 0.6.8-0ubuntu3.1 If you don't have the .1 try updating.