Bug 550221

Summary: yast2 - inconsistency on showing 'conflicts'; (maybe RFE, but should be bug)
Product: [openSUSE] openSUSE 11.1 Reporter: L. A. Walsh <suse>
Component: YaST2Assignee: Thomas Göttlicher <tgoettlicher>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P5 - None CC: tgoettlicher
Version: Final   
Target Milestone: ---   
Hardware: Other   
OS: openSUSE 11.1   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description L. A. Walsh 2009-10-26 21:09:44 UTC
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-UTF-8; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3 (.NET CLR 3.5.30729)

When I'm in Yast2, and I tell it to check for inconsistencies in my package setup, it doesn't show me "missing prerequisites", or give me the option to NOT install the packages that require specific prerequisites.

Instead, after it has supposedly finished showing me 'inconsistencies', when I hit "accept", it says, in addition to your choices, I'm going to install "XXXX" more packages that are required to install your choices...  Then there is no option to to click on 'no', or examine what packages are requiring the the extra packages.

This information should be listed in the 'conflicts' OR there should be an option to show 'missing prerequisites" as conflicts (because wanting to install package "X" may be a conflict, if I don't want to install 100 pre-req packages that it comes with!).

I'd like to see an option to examine what is requiring, 'what' pre-requisites', so I can select (or deselect).   Sometimes (often), I don't know if a package will be useful to me from the description, but I want to try it out.  Unfortunately, if it requires 50 extra support packages, I don't know that and can't know it -- all I know is some large number of packages in addition to my choices were installed.  If I later uninstall that package, there is no option or way to uninstall all of its pre-reqs that are unused by any other package.

Thus the necessity to be upfront with this information.  The dependency chains for many packages is horribly intertwined and twisted and in many cases simply _inconsequential_...  Some package may have a dep on another package, but it's if you use 'subprogram X'.  If you don't use subprog X, you'll never see a problem.



Reproducible: Always

Steps to Reproduce:
1.  No unique steps -- just pick a package that has hidden requirements.  When you finish with package selection (I was using the GUI yast2), and all conflicts have been 'resolved', when you hit accept, the hidden 'requirements' are displayed.  
2.
3.
Actual Results:  
select many packages and see a hodgepodge of added packages

Expected Results:  
give me option to deslect a pre-req and if so, I get returned to the 'conflict resolution dialog' (with the result that I'll need to press 'Accept' to accept the current package selection again after resolving the conflict).
Comment 1 Ladislav Slezák 2009-11-03 13:49:17 UTC
If you press [Accept] the displayed popup dialog has two bottons:

[Continue] - start package installation

and 

[Cancel] - go back to the package selection - you can change the selection if the list of dependent packages is not what you had expected. Then you can switch to the Installation summary view and check the autoselected packages and set Taboo to see which requires it.

Package uninstallation has been discussed several times, sorry, I don't know the current status.
Comment 3 Thomas Göttlicher 2009-11-13 14:02:31 UTC
(In reply to comment #1)
> Package uninstallation has been discussed several times, sorry, I don't know
> the current status.
This is discussed in bug #492724.

*** This bug has been marked as a duplicate of bug 492724 ***