Bug 797205

Summary:	split-provides don't work
Product:	[openSUSE] openSUSE Tumbleweed	Reporter:	Ludwig Nussel <lnussel>
Component:	libzypp	Assignee:	E-mail List <zypp-maintainers>
Status:	VERIFIED INVALID	QA Contact:	E-mail List <qa-bugs>
Severity:	Major
Priority:	P5 - None	CC:	cobexer, ismail, jengelh, lnussel, mls, werner
Version:	13.1 Milestone 1
Target Milestone:	---
Hardware:	x86-64
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Ludwig Nussel 2013-01-08 10:24:46 UTC

+++ This bug was initially created as a clone of Bug #796167 +++

looks like zypp/sat-solver doesn't properly evaluate split-provides. See bug 796167 for details and test case.

Comment 1 Ludwig Nussel 2013-03-22 08:07:58 UTC

ping!?

Comment 2 Michael Schröder 2013-03-22 12:37:44 UTC

Not a bug. You have "cryptsetup-mkinitrd" on the soft-locks list.

Note that split-provides are weak dependencies, i.e. it *must* be ok to ignore the provides. Mandatory package splits (whatever that is) can't be solved with split provides, they need to be enforced by something else.

Comment 3 Ludwig Nussel 2013-03-22 13:04:06 UTC

I wonder if that SoftLocks entry in the other bug came from the debugging session Sascha talked about. I doubt it has been there in the original zypper dup he made as the package didn't exist before. So it could be that the solver test case does not show the real situation. Just wanted to clarify that split-provides are still meant to work.

Comment 4 Jan Engelhardt 2013-04-02 13:57:32 UTC

When using --no-recommends (either by option or command line), packageand will not be processed. (See also bug #812944)

Why do I use no-recommends? Because the Recommends: in specfiles causes the installation of quite some bloat. IMO, the meaning of --(no-)recommends should not be overloaded with the special packageand(..) supplements.