https://bugzilla.suse.com/show_bug.cgi?id=1200841 https://bugzilla.suse.com/show_bug.cgi?id=1200841#c4 Stefan Hundhammer <shundhammer@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|YaST2 |libzypp Assignee|yast2-maintainers@suse.de |zypp-maintainers@suse.de QA Contact|jsrain@suse.com |qa-bugs@suse.de --- Comment #4 from Stefan Hundhammer <shundhammer@suse.com> --- So what you are looking for is in fact another solution to be proposed for this particular type of dependency problem. While I can understand your desire to get such a very specialized, dedicated solution to choose from, I don't think it is reasonably feasible; it would require too much specialized knowledge within the dependency resolver to recognize this very special case, and also to check such a very special solution exists and can be applied. Notice that this is not a property of the YaST package GUI, but of the low-level dependency resolver; the dependency resolver is what proposes the possible solutions that the user can choose from. The YaST GUI only presents them and lets the user select one of them for each individual dependency problem. So, we can ask our libzypp / dependency resolver experts if they see a chance to implement such a very special case, but IMHO that is very unlikely. Libzypp team, please add your input. -- You are receiving this mail because: You are on the CC list for the bug.