|
Bugzilla – Full Text Bug Listing |
| Summary: | Difficult to remove all software in pattern during upgrade | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Karl Cheng <qantas94heavy> |
| Component: | YaST2 | Assignee: | YaST Team <yast-internal> |
| Status: | RESOLVED WONTFIX | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P3 - Medium | CC: | ancor, dimstar |
| Version: | Current | ||
| Target Milestone: | Current | ||
| Hardware: | Other | ||
| OS: | Other | ||
| URL: | https://trello.com/c/ekwx0CRI | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | A bunch of screenshots illustrating the difficulty of removing patterns | ||
Definitely this part needs a usability revamp. But that is not trivial. Adding it to YaST Team Scrum backlog, in order to prioritize in relation to other tasks. I'll move this to TW then This has always been a side effect of the very concept of patterns: They are really just a bunch of dependencies. But the same package might be required by one or more patterns, and also by other packages. That makes removing them difficult. If you are in that kind of situation, your only chance is to switch to the patterns view in the *detailed* software selection where you can see all the packages that constitute a pattern individually, and then trying to remove them one by one. Yes, that is tedious. You will have to make many individual decisions, and that makes it very error-prone. There is no reasonably easy way to do this. And this is now 6 years old without any action. That means that nobody found this important enough during all that time to invest any development resources, even if somebody would have had a good idea how to do this. Realistically, this will not change for the forseeable future. Closing. |
Created attachment 698781 [details] A bunch of screenshots illustrating the difficulty of removing patterns I was testing an upgrade from openSUSE 13.2 to Leap 42.2 with low disk space, and (as expected) there is some red text on the summary page to remove packages or the upgrade might fail. In order to do so, I decided to click on the "Upgrade Options" and remove the "Technical Writing" pattern (say, because I no longer needed to use those tools), but this failed to remove any relevant packages. I then tried to remove the pattern and its accompanying packages using the "Packages" section. If I attempted to remove the package by clicking "Delete" on the "Technical Writing" option on the left, it did not remove any packages, even if the "Cleanup when deleting packages" option is selected. Selecting "All In This List -> Delete" prompted a number of pattern dependency issues, which YaST seemed to be unable to suggest a satisfactory method of resolving these problems. It is only if you click on the package "patterns-openSUSE-technical_writing" and click "Delete" with the "Cleanup when deleting packages" option enabled that the other packages would be removed. This seems to be some conceptual difference between "autopatterns" and actual patterns, but I found this rather confusing and unintuitive. Is there any easier way of dealing with this issue?