"Mark all Upgrades" should be grayed out if there are no upgrades

Bug #186449 reported by Endolith
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
synaptic (Ubuntu)
Triaged
Wishlist
Unassigned

Bug Description

Binary package hint: synaptic

The "Mark All Upgrades" button in Synaptic should only be active if there are actually upgrades available.

Revision history for this message
Paul Gevers (paul-climbing) wrote :

True. Wish list item I would say.

Changed in synaptic:
status: New → Confirmed
Markus Korn (thekorn)
Changed in synaptic:
importance: Undecided → Wishlist
Revision history for this message
Tomasz Chrzczonowicz (tch) wrote :

I guess it's a bug as it's misleading.

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

It'd be quite trivial to set the enabled state of the button based on the number of upgradeable packages available.

However, while it is quite easy to see which packages have a higher version available, it cannot be known if the package can actually be upgraded until it is actually attempted to mark the package for upgrade, since that is when dependency resolution is done.

How I've handled this for the Muon package manager is to set the enabled state for the upgrade action solely based on the number of upgraded packages, but it also checks after attempting to mark the packages as upgraded to see if any packages were actually marked. If not, it gives a little explanatory message telling why, in some cases, packages may not be upgradeable, be it due to a data package common to all Ubuntu-supported architectures, archive skew, or plain broken packages.

It shouldn't be too difficult to somebody familiar with GTK+. (But alas, I don't really know GTK+, being a Qt man myself)

Changed in synaptic (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
Robert Roth (evfool) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #595127, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.