Bug 392971

Summary: Impossible to deselect Novell AppArmor from Software-Selection
Product: [openSUSE] openSUSE 11.0 Reporter: Lars Müller <lmuelle>
Component: YaST2Assignee: Klaus Kämpf <kkaempf>
Status: RESOLVED FIXED QA Contact: Jiri Srain <jsrain>
Severity: Enhancement    
Priority: P5 - None CC: coolo, dmacvicar, jsuchome
Version: Factory   
Target Milestone: ---   
Hardware: All   
OS: openSUSE 11.0   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: YaST log of the deselect action

Description Lars Müller 2008-05-21 08:24:15 UTC 
At the installer level in update mode it's impossible to deselct 'Novell Apparmor'.

I tried right and left mouse click.  The tick to select for install always stays.
Comment 1 Lars Müller 2008-05-21 08:25:15 UTC 
Created attachment 217134 [details]
YaST log of the deselect action
Comment 2 Jiří Suchomel 2008-05-21 08:26:58 UTC 
You have to taboo it, than it works.

If it is not what you want, pattern requirements must be changed: reopen and assign to coolo.
Comment 3 Lars Müller 2008-05-21 10:18:35 UTC 
That's not what I want.  If there is a reason why this should not be done by the user there should be a big warning.  But currently it silently fails.
Comment 4 Lars Müller 2008-05-21 10:19:22 UTC 
Coolo: This might be to late for 11.0 but might be valid to check in the time of 11.1.
Comment 5 Stefan Hundhammer 2008-05-21 10:36:10 UTC 
This might be a misunderstanding due to the new semantics of patterns: They are displayed as "installed" if they are satisfied OR if the user explicitly requests them. 

A pattern is satisfied if all packages it requires are installed or selected for installation. If a pattern has few "requires", but many "recommends", this could lead to the effect you observed: You can't seem to get rid of that pattern -- even though it might not hurt you because nothing you really don't want gets installed.

You could try to go to the detailed package selection and have a look which of the packages of that pattern get installed or updated.


Jiri: I am not sure if "Taboo" is any more possible for patterns. AFAIK it would not do anything useful any more now that pattern states are no longer written to the target system.
Comment 6 Lars Müller 2008-05-21 10:55:28 UTC 
In the particular case the intention was not to install any AppArmor package.  And till now I expected the decision not to install a pattern would result in not installing packages of the pattern not required by other packages.

From Stefan's explanation this isn't the case.  Therefore YaST should display some message if a users is doing the action in question.  If it is possible to detect such a usage.

I fear the current approach doesn't fit to the expectations of the majority of users.  On the other side the question is how many users are modifying the package selection.
Comment 7 Klaus Kämpf 2008-05-23 07:17:02 UTC 
Pattern removal is still unsolved for Code11. There was a proposal how to fix it which was rejected.
Needs to be re-visited for 11.1
Comment 8 Klaus Kämpf 2008-09-09 10:18:57 UTC 
This should be fixed in 11.1 now.