Bug 869440

Summary:	zypper dup includes recommends
Product:	[openSUSE] openSUSE Tumbleweed	Reporter:	Sascha Peilicke <speilicke>
Component:	libzypp	Assignee:	E-mail List <zypp-maintainers>
Status:	RESOLVED WONTFIX	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P3 - Medium	CC:	mls, raul.malea
Version:	13.2 Milestone 0
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Sascha Peilicke 2014-03-20 16:14:09 UTC

Since recently, zypper dup selects recommended packages. This is very odd since "--no-recommends" and "solver.onlyRequires = false" in /etc/zypp/zypp.conf have other unwanted implications. zypper up is still working as expected.

2014-03-20 16:02:28 <1> bort.suse.de(10401) [libsolv++] PoolImpl.cc(logSat):109 dontinstallrecommended=0, addalreadyrecommended=1

Comment 1 Michael Andres 2014-03-24 15:56:39 UTC

Zypper dup always had 'addalreadyrecommended=1'. We did not change this.
Zypper dup is intended to also update language and hardware supporting packages.

Comment 2 Sascha Peilicke 2014-03-24 16:24:19 UTC

Well, in practice it pulls in >500mb 32bit packages, all patterns, the GNOME stack (I use KDE) and more on Factory. All I can say as this behavior appeared maybe a month ago and I haven't done a single dist-upgrade without --no-recommends.

Comment 3 Michael Andres 2014-03-26 07:42:59 UTC

Yes, I see your point. While one probably wants to get new language and hardware supporting packages, 'ordinary' package recommendations are not desired. Unfortunately you currently cant get one without the other when using addalreadyrecommended=1.

We could probably solve this if the resolver allows to reevaluate namespace dependecies (language, hardware, filesystems) only in addalreadyrecommended.

Comment 4 Tomáš Chvátal 2018-04-13 17:21:40 UTC

This is automated batch bugzilla cleanup.

The openSUSE Tumbleweed changed its development model at the end of
year 2014. [1]
Which means that most of the older bugs are reported against completely
different product than the current release of openSUSE Tumbleweed.

There is very high probability that this bug is no-longer relevant at all.
As a result we are closing this bug.

If you can reproduce this bug against a current Tumbleweed installation of
openSUSE, or you can still observe it under openSUSE Leap 15.0, please
feel free to reopen this bug.

Thank you for reporting this bug and we are sorry it was not resolved
under the old product.

[1] https://en.opensuse.org/Portal:Tumbleweed