I have a package which I have set on hold, which means it would be updated. Unfortuneately this means my update notification is permanently notifying me about available updates so I have to click from time to time in order to check if there is something else then the update which I have set on hold. I think the behaviour of notifying about packages "on hold" should be handled as follows. - No notification in the icon - If the user clicks on the icon to see the updates, he then sees * XXX updates * XX security updates * X package(s) on hold The user then somewhere has an option update the package on hold anyway, but is not asked on every updated if he wishes to do that.
Does PackageKit even know about "on hold" packages marked with apt?
Can not tell, but even good old synaptic does.
Synaptic is a frontend to apt, so I would expect it to. Discover is a frontend to PackageKit, which is itself an abstraction layer above apt, yum, dnf, zypper, pacman, etc.
Hmm, at least it respects packages which are marked as on hold by not updating them.
You can check with apper, it should be able to show if a package is set on hold according to packagekit.
*** Bug 395945 has been marked as a duplicate of this bug. ***
Updates on hold are currently just not being listed. Please try reproducing it and get back to me with details. I don't really want to be showing the user that a said package is on hold on the other hand, if the users decided to put packages on hold so, it's their own responsibility to eventually un-hold it. It's easy to enable/disable holdness on apt distros using Muon.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!