|
Bugzilla – Full Text Bug Listing |
| Summary: | no yast2 modules selected for installation | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Distribution | Reporter: | Per Jessen <per> |
| Component: | Installation | Assignee: | E-mail List <yast2-maintainers> |
| Status: | RESOLVED WONTFIX | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | jreidinger, mpluskal, per |
| Version: | Leap 42.2 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Per Jessen
2016-08-07 17:54:41 UTC
This appears to happen when I deselect grub2. Correction, by de/selecting "ruby2.1-rubygem-cfa_grub2" , "Patterns: YaST System Administration" is also automagically de/selected. (In reply to Per Jessen from comment #2) > Correction, by de/selecting "ruby2.1-rubygem-cfa_grub2" , "Patterns: YaST > System Administration" is also automagically de/selected. Well it seems that you removed one of dependencies of this pattern - deselecting patttern if its dependencies are deselected is if I recall correctly default and intended behavior for quiete some time. Please elaborate why do you think that this is a bug. (In reply to Martin Pluskal from comment #3) > (In reply to Per Jessen from comment #2) > > Correction, by de/selecting "ruby2.1-rubygem-cfa_grub2" , "Patterns: YaST > > System Administration" is also automagically de/selected. > > Well it seems that you removed one of dependencies of this pattern - > deselecting patttern if its dependencies are deselected is if I recall > correctly default and intended behavior for quiete some time. > > Please elaborate why do you think that this is a bug. Deselecting "ruby2.1-rubygem-cfa_grub2" which appears to be grub2 related should not cause deselection of the Yast System Administration pattern. I don't use grub2 in this xen guest, so deselecting it make sense. It's directly required by yast2-bootloader. You could try to redesign yast2-bootloader and split off specific bootloader type support in subpackages like yast2-bootloader-grub2 but since y2-bl supports _only_ grub2, this seems a bit over-engineered to me. I think it's ok to live with the fact that y2-bl has the ability to read configs of bootloaders that aren't installed. |