|
Bugzilla – Full Text Bug Listing |
| Summary: | system upgrade: keep packages with no replacement if they are contain only data | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.0 | Reporter: | macias - <bluedzins> |
| Component: | Update Problems | Assignee: | Klaus Kämpf <kkaempf> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Enhancement | ||
| Priority: | P5 - None | ||
| Version: | Alpha 2 | ||
| Target Milestone: | Future/Later | ||
| Hardware: | i586 | ||
| OS: | Other | ||
| Whiteboard: | FATE303267 | ||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
macias -
2007-10-25 13:17:15 UTC
Klaus wanted to revisit this topic anyway. Handling dropped/unmaintained packages is in general an area where we need to improve the user experience. The last idea discussed was to provide a list of packages we _want_ to be dropped and let the package solver figure out which packages need to be removed too. Right, this needs solver support to provide - a list of 'must remove' packages, since their requirements cannot be fulfilled after upgrade. These packages are scheduled for removal, user can selectively override. - a list of 'can remove' packages, their requirements are still fulfilled after upgrade. These packages are schedules for stay, user can selectively override. (Since its an enhancement request, I'm moving the product to 'OpenSUSE 11.0') Tracked as Code11 enhancement request. mass reopening of later+remind bugs of 11.0 Implemented in 11.1 |