Bug 381244

Summary:	Bad report on driver conflicts
Product:	[openSUSE] openSUSE 11.0	Reporter:	Klaus Kämpf <kkaempf>
Component:	libzypp	Assignee:	Stefan Schubert <schubi>
Status:	RESOLVED DUPLICATE	QA Contact:	Duncan Mac-Vicar <dmacvicar>
Severity:	Critical
Priority:	P5 - None	CC:	coolo, dmacvicar, mls
Version:	Beta 1
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	y2log.bz2 showing the details

Description Klaus Kämpf 2008-04-18 10:09:41 UTC

See https://bugzilla.novell.com/attachment.cgi?id=208889
selecting "Console tools" raises a conflict with kernel-default

(System update 10.3->11.0beta1)

Comment 1 Klaus Kämpf 2008-04-18 10:11:11 UTC

Created attachment 208891 [details]
y2log.bz2 showing the details

Comment 2 Klaus Kämpf 2008-04-18 11:04:07 UTC

No, it has nothing to do with "Console tools", its a driver (iwlwifi-xen) problem.

And it looks like two bugs to me

1. Bad report on the real cause of the conflict

2. Pattern selector behaves different from package selector in YaST. The latter does an initial solver run, the former doesn't.

Comment 3 Stephan Kulow 2008-04-19 16:17:48 UTC

the problem has always been with the distribution upgrade algorithm. It generates conflicting requests - but without test case this is pretty hard to say. So where is yours?

Comment 4 Klaus Kämpf 2008-04-21 10:34:22 UTC

Where do I request a "solver test case" in the pattern selection dialog ?
I've looked for it but wasn't successful :-(

Comment 5 Stefan Hundhammer 2008-04-21 11:19:02 UTC

(In reply to comment #4 from Klaus Kaempf)
> Where do I request a "solver test case" in the pattern selection dialog ?

It's available in the package selector.

"Details" button -> package selector -> "Extras" menu -> "resolver test case".

Comment 6 Stefan Schubert 2008-04-22 11:04:31 UTC

Klaus if you have made a system update:
"(System update 10.3->11.0beta1)" 
A testcase will be automically generated and stored under /var/log/updateTestcase/

Comment 7 Klaus Kämpf 2008-04-22 11:24:27 UTC

Yes, thats what I did.
But I don't have /var/log/updateTestcase (nor /var/log/YaST2/updateTestcase)
:-(

Could it be that the testcase is created in the inst-sys (ramdisk) ... ?

Comment 8 Stephan Kulow 2008-04-22 12:02:32 UTC

let's take the bug of the expert to dup this one here :)

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

Comment 9 Stefan Schubert 2008-04-22 12:48:01 UTC

"Could it be that the testcase is created in the inst-sys (ramdisk) ... ?"
That's I have feared..... I should put it to /var/log/YaST

Comment 10 Klaus Kämpf 2008-04-22 12:52:31 UTC

Well, in the update case you already have the target system mounted and could write directly there.

Comment 11 Stefan Schubert 2008-04-22 13:53:36 UTC

comment #10 Thank you for the hint. I have changed.