Bug ID 1194494
Summary Package conflict resolution dialog in Yast is frustrating and cumbersome for large number of conflicts
Classification openSUSE
Product openSUSE Tumbleweed
Version Current
Hardware 64bit
OS openSUSE Tumbleweed
Status NEW
Severity Enhancement
Priority P5 - None
Component YaST2
Assignee yast2-maintainers@suse.de
Reporter bob@muhlenberg.edu
QA Contact jsrain@suse.com
Found By ---
Blocker ---

If you are trying to upgrade and encounter a large number of package conflicts
( say thousands of them ) the behavior of the GUI is extremely cumbersome or
perhaps buggy.

In the Yast2 conflict resolver dialog, the list which presents a radio button
choice for each conflict, there are no defaults nor a way to resolve largely
cosmetic conflicts like vendor change.   I seem to remember there at least
being defaults, so perhaps this is a bug when huge numbers of conflicts are
found.

As an example, TeXlive, which has 8,800 separate packages, generates 8,800
separate conflicts.  There needs to be a "yes, for the love of God, I get it,
change of vendor, blah, blah, blah" option as there is no way to resolve this
at install time.

Even if you do decide to power through it an hit space bar to select the first
option ( usually the correct one ) and press TAB to continue to the next
conflict, the list of conflicts has a horizontal scroll bar, and the entire
list is shifted to the left - meaning you cannot see the radio buttons and
option text.   Since TAB seems to intentionally navigate to the next conflict,
it should probabaly not be scrolling the pane hard left and leave the H-scroll
position unchanged.  ( IMO its better to leave the H-scroll position alone than
mess with it. )

A means to auto advance to the next decision might make clicking viable. 
However manually scrolling is necessary.  For a 1000 item list, this is
challenging.

After making changes, Try Again spins for a while then seems to return you to
the same list, without having refreshed it - same items are selected,
horizontal scroll position is the same.   I'm not sure it is actually working
or doing anything other than returning you to the same dialog.  It may not
actually be functioning properly processing a huge list.

Some of these are still issues when only a couple conflicts are present, but it
is easier to navigate through it.


You are receiving this mail because: