|
Bugzilla – Full Text Bug Listing |
| Summary: | Yast package management: "all in this list" does not work as expected | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.1 | Reporter: | Klaus Kämpf <kkaempf> |
| Component: | YaST2 | Assignee: | Stefan Hundhammer <shundhammer> |
| Status: | RESOLVED WONTFIX | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Enhancement | ||
| Priority: | P3 - Medium | CC: | dmacvicar, ma |
| Version: | Beta 1 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
Complete logs incl. solver testcase
Screenshot |
||
|
Description
Klaus Kämpf
2008-09-23 09:30:48 UTC
"Choosing "all in this list" in YaST GUI, trying to reset all package updates does not work." Do you have a testcase for that case ? The first one was solved by fixing missing vendor entries. Still happens with Beta4. After a successful 'zypper dup', yast still shows 'k3b' as 'needs update' (1.0.5-47.2 installed, 1.0.5-48.6 available). Doing an 'all in this list -> keep' still leaves k3b on 'update' Created attachment 250248 [details]
Complete logs incl. solver testcase
Created attachment 250251 [details]
Screenshot
k3b is installed I have k3b set for update: Install U_Tu_(3032)k3b-1.0.5-48.6.x86_64(openSUSE-dvd 11.1-0) All_in_this_list/do_not_install does not change the status. Note: The "do not install" and "taboo" in the menue "Package" is not available, which is correct, cause only "keep", "update" is valid. "keep", "update" does work with "all in this list" correctly. So, some state changes are not valid for all packages in the list. The problem is how to show this the user in a proper way. I set it to enhancement. Perhaps HuHa has an idea in the future. We just talked about that: There is no reasonable way to do this differently from the UI perspective. It is perfectly normal that actions like "all in this list..." are not applicable to every item in the list, yet you can invoke them. The result is always that the action is performed on those items where it can be performed, silently ignoring the others. The visual feedback is the status change on those items where the action could be performed. There is only the exceptional case that the action cannot be performed on any of the items. In that case (and only in that case) it might make sense to disable the action in the menu. But this is expensive in terms of performance: For the normal status change action, the status of the currently selected package has to be checked, and the permitted status change actions in the context menu have to be enabled or disabled accordingly. For the actions in "all in this list", the status of every package in the list would have to be checked, and for "all packages" the status of all packages, regardless whether or not it is currently displayed in the list. This would have to be done upon every status change done by the user, and after every solver run (because the solver can change any number of package states). This might easily bog down the entire application for this fringe case. I don't think this is a good idea. |