Bug 903632

Summary: Yast suggesting uninstalled packages for installation every time
Product: [openSUSE] openSUSE Distribution Reporter: Forgotten User xRcrmyYBVX <forgotten_xRcrmyYBVX>
Component: YaST2Assignee: Martin Vidner <mvidner>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P2 - High CC: axel.braun, forgotten_GYimNF7a5V, forgotten_xRcrmyYBVX, jnelson-suse, jreidinger, ma, mls, mvidner, stakanov
Version: 13.2 RC 1   
Target Milestone: ---   
Hardware: Other   
OS: Other   
URL: https://trello.com/c/fc9pedpd
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: Yast installation summary showing all uninstalled packages should be installed
Clean y2log

Description Forgotten User xRcrmyYBVX 2014-11-03 09:07:52 UTC
In openSUSE 13.2, I uninstalled all 'texlive-*-doc' packages and multiple others (non texlive things).

Now, when starting Yast Software Manager, on the 'Installation Summary' page it shows all those 'texlive-*-doc' packages incl the other uninstalled software to be installed again.

I have to left-click and chose 'Do not install' to all packages in the 'Installation Summary' screen EVERY TIME I start the software manager.

Note that zypper does not recommend to install the above mentioned packages. The Yast behaviour seems to be triggered by the 'Suggests: texlive-doc' of some package I have installed.
Comment 1 Forgotten User xRcrmyYBVX 2014-11-03 09:12:54 UTC
Created attachment 612153 [details]
Yast installation summary showing all uninstalled packages should be installed

I just uninstalled all the Network Manager stuff plus the 'texlive-*-doc' packages. This situation repeats at every start of the Software Manager!
Comment 2 Jon Nelson 2015-01-10 00:44:23 UTC
Seems to be related to bug 904870.
Comment 3 Forgotten User xRcrmyYBVX 2015-01-10 11:27:12 UTC
(In reply to Jon Nelson from comment #2)
> Seems to be related to bug 904870.

unfortunately I get an access denied for that bug. Is it security or SLES related?
I have an SLES subscription as well, how do I get access to SLES bugs then?
Comment 4 Axel Braun 2015-02-11 14:09:36 UTC
(In reply to Joschi Brauchle from comment #3)
> > Seems to be related to bug 904870.
> 
> unfortunately I get an access denied for that bug. Is it security or SLES
> related?
> I have an SLES subscription as well, how do I get access to SLES bugs then?

Same problem for me. This top-secret-bug is marked as fixed, but that has obviously not hit the openSUSE tree so far?
Comment 5 Josef Reidinger 2015-02-11 14:17:13 UTC
(In reply to Axel Braun from comment #4)
> (In reply to Joschi Brauchle from comment #3)
> > > Seems to be related to bug 904870.
> > 
> > unfortunately I get an access denied for that bug. Is it security or SLES
> > related?
> > I have an SLES subscription as well, how do I get access to SLES bugs then?
> 
> Same problem for me. This top-secret-bug is marked as fixed, but that has
> obviously not hit the openSUSE tree so far?

Calm down boys, Jon probably make mistake and post wrong number as I check that bug and it is for different novell product (even not suse product) and not related at all. I am removing need info as Lada probably need different information.
Comment 6 Ladislav Slezák 2015-02-11 14:25:27 UTC
Could someone attach Yast logs? Libzypp should rememeber the user deselected packages and should not select them again later.

Any idea how could I reproduce it? On my system I do not have any texlive-* package installed and Yast does not preselect any...
Comment 7 Axel Braun 2015-02-11 14:28:19 UTC
Please see bug 908740
Comment 8 Forgotten User xRcrmyYBVX 2015-02-11 14:49:53 UTC
Created attachment 622827 [details]
Clean y2log
Comment 9 Ladislav Slezák 2015-02-12 15:47:29 UTC
*** Bug 908740 has been marked as a duplicate of this bug. ***
Comment 10 Ladislav Slezák 2015-02-12 16:12:50 UTC
Um, I just reproduced the problem on my machine - I uninstalled some recommended packages by the KDE pattern like choqok, kmail... and after starting the package manager Yast automatically preselect them in every run.

In the past libzyp remembered the packages which were explicitly deselected by user and stored them to /var/lib/zypp/SoftLocks file (right-click in the Installation Summary tab and select All in this list -> Do not install, Accept the changes). 

But the softlocks have been removed from libzypp (see bnc#863275#c4) and this does not work anymore...

The workaround is to check option Options -> "Ignore Recommended Packages for Already Installed Packages" to prevented them to be selected again.


Michaels, any idea how this should be solved in Yast?
Comment 11 Ladislav Slezák 2015-02-12 16:14:10 UTC
(Adding Michaels to CC....)
Comment 12 Michael Andres 2015-02-12 16:55:02 UTC
>  SATResolver.cc(solving):495   ADD_ALREADY_RECOMMENDED	= 1

There are several bugs (#905802,#902394,...) addressing the fact that yast insists on solving with ADD_ALREADY_RECOMMENDED set True (ignoreAlreadyRecommended set False).

Un-checking / not using the option is no workaround, it's the solution.
Comment 13 Axel Braun 2015-02-12 20:06:21 UTC
A 'normal' user doesn't even know about that option, so the default should be to set it to 'dont select recommended
Can that be set in the SUSE standard?
(and where is it set?)
Comment 14 Axel Braun 2015-02-20 10:06:32 UTC
Ladislav Slezak from comment #10)
> 
> The workaround is to check option Options -> "Ignore Recommended Packages
> for Already Installed Packages" to prevented them to be selected again.

Hm, I cant confirm this working.
If I set the tick in the YaST2 Frontend, it still insists on installing a couple of deselected patterns...
Comment 15 Stakanov Schufter 2015-03-18 14:23:52 UTC
For what I have seen (further your mentioning [Bug 854560]) this is still the case but can be avoided (at least for taboo listing if one is not using apper and uninstalls it or does simply mot start it. Since I uninstalled apper and I am using purely yast the problem did ---up to now-- not occur again. Before it did, also with 13.2. 

Look also, if you have a "pattern" rpm installed for this feature. A pattern package will try to force installation of such packages even if you do not want. If the pattern is installed, then you will have to take it off but you may have to confirm the packages you want to stay afterwards, otherwise they may be uninstalled as well. That may be a lot of work.
Comment 16 Forgotten User xRcrmyYBVX 2015-05-06 11:51:53 UTC
So I'm still suffering from this problem on some machines I am administering on a daily basis. Is there any progress?
Comment 17 Ladislav Slezák 2015-05-06 16:36:59 UTC
Sorry, no progress yet...
Comment 18 Lukas Ocilka 2015-06-23 07:41:37 UTC
Martin, is this also covered by the fix you are working on?
Comment 19 Martin Vidner 2015-06-23 08:35:54 UTC
Oh, another one, welcome to the party :) The main bug is https://bugzilla.suse.com/show_bug.cgi?id=902394

It is definitely a related problem, but there are many places in code that manipulate the flag, so I cannot say for sure that my changes already fix this. I'll look and report back.
Comment 20 Martin Vidner 2015-06-24 14:31:58 UTC
(In reply to Axel Braun from comment #14)
> > The workaround is to check option Options -> "Ignore Recommended Packages
> > for Already Installed Packages" to prevented them to be selected again.
> 
> Hm, I cant confirm this working.
> If I set the tick in the YaST2 Frontend, it still insists on installing a
> couple of deselected patterns...

Axel, can you be specific please? You run yast2 sw_single, ensure "Ignore ... Already..." is enabled, select something (or not?) and which patterns get selected?

If they get recommended by a newly selected package/pattern then that is handled in https://bugzilla.opensuse.org/show_bug.cgi?id=900853 where we make the overall flag "Install Recommended" configurable.
Comment 21 Axel Braun 2015-06-25 12:59:42 UTC
(In reply to Martin Vidner from comment #20)

> Axel, can you be specific please? You run yast2 sw_single, ensure "Ignore
> ... Already..." is enabled, select something (or not?) and which patterns
> get selected?
> 
> If they get recommended by a newly selected package/pattern then that is
> handled in https://bugzilla.opensuse.org/show_bug.cgi?id=900853 where we
> make the overall flag "Install Recommended" configurable.

I have set up a new VM with 13.2, fully patched, and can actually not reproduce the problem anymore.
Either on installation of a package from a pattern, as well on installation of a new package.

Zypper version is 1.11.23

Do you want me to check against an unpatched 13.2?
Comment 22 Martin Vidner 2015-06-25 13:42:50 UTC
> Do you want me to check against an unpatched 13.2?

No, this is enough for me, thanks!

I will consider this a duplicate of bug 902394.

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