Bug 158895

Summary:	dependency conflict
Product:	[openSUSE] SUSE Linux 10.1	Reporter:	Andreas Klein <asklein>
Component:	YaST2	Assignee:	Stefan Schubert <schubi>
Status:	RESOLVED DUPLICATE	QA Contact:	Klaus Kämpf <kkaempf>
Severity:	Normal
Priority:	P5 - None	CC:	schubi, suse-beta, vetter
Version:	Beta 8
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	/tmp/conflict.png /tmp/y2logs.tgz

Description Andreas Klein 2006-03-17 00:55:52 UTC

YaST2 shows a dependency conflict window, but does not show the conflicts in it.
See screenshot.

Comment 1 Andreas Klein 2006-03-17 00:56:35 UTC

Created attachment 73442 [details]
/tmp/conflict.png

Comment 2 Andreas Klein 2006-03-17 01:01:56 UTC

Created attachment 73443 [details]
/tmp/y2logs.tgz

Comment 3 Andreas Klein 2006-03-17 02:14:28 UTC

One problem is lprng.
- do a default installation
- verify, that the dependency check says, that all dependencies are ok
- select lprng which should conflict with cups
- check the dependencies
==> You will see an empty dependency conflict window
Ok, try again shows the empty dependency conflict window again and again.

Comment 4 Klaus Kämpf 2006-03-17 15:28:13 UTC

Empty conflict window is certainly a bug.

Comment 5 Stefan Hundhammer 2006-03-17 15:52:14 UTC

Definitely. This means that Resolver::resolvePool() returned 'false' (no success), yet the problem list it returns upon Resolver::problems() is empty. This should not happen.

Comment 6 Stefan Schubert 2006-03-18 08:58:12 UTC

I assume, thats my bug;-)

Comment 7 Stefan Schubert 2006-03-18 13:14:06 UTC


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