|
Bugzilla – Full Text Bug Listing |
| Summary: | dependency checking broken | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Rasmus Plewe <rplewe> |
| Component: | Installation | Assignee: | E-mail List <bnc-team-screening> |
| Status: | RESOLVED INVALID | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Beta 4 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
You did read the big, fat warning when entering the dialog ?! ;-) But logs might be a bit helpful to decide between 1, 2, and 3 ... No, for the warning to be read it would have to have been red also. ;-) And the warning said "conflict resolution should work". You will get the logs as soon as I've got access to the machine again - it's currently installing NLD. Rasmus: The installer in beta4 is really in a very early stage... these issues are known.
From an official mail:
o Only adding of selections works. If you want to remove a
selection, remove all packages in that selection and run the
resolver manually with the "Check" button.
We are working on this in the normal development process, so I close this bug now, there will probably be countless bugs of that sort ;)
Just for clarification: What you're quoting is *exactly* what I did: I added selsctions. But, of course, you're absolutely right: there will be countless bugs of this sort coming in, I'm sure. ;-) |
During installation, I selected a couple of additional selections ("All of KDE", "Experienced User"...). When clicking "ok", the system went into "checking dependencies" and than back to the Installation Settings screen. Tradition shows that, when selecting additional selections, you are presented with a long list of packages that will get installed additionally, or even conflicts. This leads to three possibilities: 1. The selections are complete and conflict-free. 2. Those conflicts are handled silently. 3. The dependency checking is broken. Of these, 1. is very, very unlikely, 2. would be very bad, which leaves 3.