Bug 302496 - dependency solver does not recognize the all-conflicts-solved state
Summary: dependency solver does not recognize the all-conflicts-solved state
Status: RESOLVED FIXED
: 172115 303934 (view as bug list)
Alias: None
Product: openSUSE 10.3
Classification: openSUSE
Component: Installation (show other bugs)
Version: Beta 1
Hardware: PowerPC Linux
: P5 - None : Critical (vote)
Target Milestone: ---
Assignee: Stefan Schubert
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-08-22 12:59 UTC by Olaf Hering
Modified: 2008-07-16 15:40 UTC (History)
1 user (show)

See Also:
Found By: Development
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
openSuSE-10.3b2-no-deps.png (56.99 KB, image/png)
2007-08-22 12:59 UTC, Olaf Hering
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Olaf Hering 2007-08-22 12:59:04 UTC
Created attachment 159044 [details]
openSuSE-10.3b2-no-deps.png

openSUSE-10.3-Beta2-DVD-ppc-Build935 on iseries

I added factory, factory-extra and factory-debuginfo (or whatever gets automatically offered in first stage).
Not all package dependencies could be resolved.
It offered me gstreamer-something and an 'do a full resolver run (?)'.

Once that run was done, every new 'Check' run shows an empty window as shown in the screenshot.
All I can do is to leave with cancel, which most likely gives an incomplete package list because many patterns are not selected (as shown in the screenshot).
Comment 1 Olaf Hering 2007-08-22 14:26:08 UTC
logs can be found in ~olh/bugs/302496/
Comment 2 Stefan Schubert 2007-08-24 07:55:07 UTC
Logs, with testcase. Great !!!!
Comment 3 Stefan Schubert 2007-08-24 08:46:51 UTC
The solver has aborted after an timeout and had no solution cause you had selected 
'do a full resolver run' which means "take all packages with compatible architecture"
So the solver does not return an error message although he was NOT successful.

A pober solution would be

Have no solution cause timeout has been reached:

Solution:
- Ignore timeout
- Regard packages with the best architecture only.
Comment 4 Stefan Schubert 2007-08-24 08:59:23 UTC
The intesting part is also in different repos:

<package>
	<name>sed</name>
	<history>
	<update>
		<arch>ppc</arch>
		<version>4.1.5</version><release>58</release>
	</update>
	</history>
	<provides>
		<dep name='base:/bin/sed' kind="package" />
		<dep name='/bin/sed' kind="package" />
		<dep name='/usr/bin/sed' kind="package" />
		<dep name='sed' op='==' version='4.1.5' release='58' kind="package" />
	</provides>
</package>



AND

<package>
	<name>sed</name>
	<history>
	<update>
		<arch>ppc</arch>
		<version>4.1.5</version><release>58</release>
	</update>
	</history>
	<provides>
		<dep name='base:/bin/sed' kind="package" />
		<dep name='sed' op='==' version='4.1.5' release='58' kind="package" />
	</provides>
</package>
Comment 5 Stefan Schubert 2007-08-27 15:01:33 UTC
*** Bug 303934 has been marked as a duplicate of this bug. ***
Comment 6 Stefan Schubert 2007-08-29 11:33:39 UTC
I have fixed it as described in comment #3
Comment 7 Stefan Schubert 2007-09-04 08:44:15 UTC
*** Bug 172115 has been marked as a duplicate of this bug. ***