|
Bugzilla – Full Text Bug Listing |
| Summary: | software installer does not ask when two packages provide the same dependency | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Holger Hetterich <hhetter> |
| Component: | YaST2 | Assignee: | Klaus Kämpf <kkaempf> |
| Status: | RESOLVED FIXED | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | suse-beta |
| Version: | Beta 7 | ||
| Target Milestone: | --- | ||
| Hardware: | i386 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Holger Hetterich
2006-03-09 11:32:06 UTC
Raising severity. Well, the resolver is designed to resolve dependencies and create a consistent system. As it comes from ZENworks, its mostly aimed at automatic/batch processing (task based) and not interactive behaviour. So it tries to compute a solution automatic without user feedback. The current heuristics look at smallest package sizes and smallest number of changes. (If the solver would ask for every case where alternatives have to be decided, people would probably get pretty annoyed ;-)) So the "half-baken" wesnoth experience can only be prevented by adding package dependencies and help the solver installing a "full-baken" experience. Klaus, let's inform everybody on packagers mailing list about this. Developers should be aware of this. In this specific case, I expect the following to work: Add to wesnoth.spec file: Recommends: wesnoth-data-full Requires: wesnoth-data-set wesnoth-data-full should require wesnoth-data-small (it does AFAIK). Thank you for the explanation, Andreas and Klaus. I changed wesnoth.spec to Recommends: wesnoth-data-full which should fix my problem, will check the package in the next hours. AFAIK, this is a change of behaviour of YaST, it should be documented. |