http://bugzilla.suse.com/show_bug.cgi?id=1162143 http://bugzilla.suse.com/show_bug.cgi?id=1162143#c7 --- Comment #7 from Rodion Iafarov <riafarov@suse.com> --- (In reply to Stefan Hundhammer from comment #5)
To clarify some more:
The behavior to have a candidate version that is not the same as your installed version is perfectly normal. Normally, the latest version is also the candidate version; a retracted version, however, will never be a candidate version (libzypp / libsolve make sure of that).
Just because there is a different version that is considered the candidate version does not mean that the package selector automatically upgrades (or downgrades) to that version; you still need to do that manually if you wish to upgrade.
To see this, just do "zypper refresh", start the Qt package selector, select the "Installation Summary" view, make sure the "Keep" status is checked on the left side and sort for column "Installed (Available)". All blue versions have a newer version available. Click on any of them and switch to the "Versions" details view. You will see that every single of those blue packages has a different version preselected than is installed; those are the candidates that you will get when you choose to upgrade. But it will not set those blue packages to "Upgrade" if you don't tell it to do that.
This behavior is perfectly normal and absolutely desired.
Main point is that current behavior is not obvious. In ncurses it's even more confusing as we have unnamed column with x in it and then status, e.g. `i` for installed. I would expect that they select same version of the package when user has selected it, if not, then it should do what it shows in the UI. It does neither of two, leaving as it is. In qt at least we have installed version being shown as label, but that's also confusing as it appears like there is another version in the main repo, even though it's same version. So in case you disagree, that it might be confusing for the customers, we can leave it as invalid and I guess we can also stop wasting your time and not raise such issues in future as 99% of UX issues are ignored with similar arguments. You don't need to explain how we can make it work, and there are zypper coomands. I didn't use this module much, but I can tell you that when I expected some change and window got simply closed, so I had to start all over, wasn't best experience. If it's desired that way - we can improve it with minor changes. So, as stated above, if there is no interest in such feedback (and I don't know better place than bugzilla for such discussions), we won't waste your time on explaining how it's desired to work and raise only functional issues. -- You are receiving this mail because: You are on the CC list for the bug.