Bug 334810

Summary: YaST sw management selects newest (possibly wrong) versions of dependent packages
Product: [openSUSE] openSUSE 11.1 Reporter: Petr Cerny <pcerny>
Component: libzyppAssignee: Michael Andres <ma>
Status: RESOLVED FIXED QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P3 - Medium CC: davejplater, dmacvicar
Version: Factory   
Target Milestone: ---   
Hardware: x86-64   
OS: openSUSE 10.3   
Whiteboard:
Found By: Development Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: y2log before selecting "Accept" button
screenshot showing installed package
screenshot showing newly selected installed package (from wrong repository)
screenshot showing warning about incompatible versions
y2logs after selecting -devel package
screenshot: missing dependencies (wron vendor) warning
screenshot: available package versions

Description Petr Cerny 2007-10-18 12:07:54 UTC
Created attachment 179218 [details]
y2log before selecting "Accept" button

When using multiple repositories (10.3 and Packman in my case) which have different versions of the same packages, the dependency solver always selects the newest version of package without any regards to other already installed packages.

Example:

1) install fftw3 from openSUSE 10.3 [fftw3-3.1.2-62]
2) select either fftw3-devel or "install all matching -devel" and fftw3-devel-3.1.2-142.pm.3 (i.e. package from Packman repository) gets selected
3) resolver complains about missing dependencies (due to different package vendor)

Such warnings can get extremely confusing and annoying for users.

Also note that higher release of a package in repository1 isn't necessarily to be more up-to-date than lower release in repository2.
Comment 1 Petr Cerny 2007-10-18 12:12:43 UTC
Created attachment 179221 [details]
screenshot showing installed package
Comment 2 Petr Cerny 2007-10-18 12:12:48 UTC
Created attachment 179222 [details]
screenshot showing newly selected installed package (from wrong repository)
Comment 3 Petr Cerny 2007-10-18 12:12:52 UTC
Created attachment 179223 [details]
screenshot showing warning about incompatible versions

(also note superfluous messages about glibc and bash)
Comment 4 Petr Cerny 2007-10-18 12:15:15 UTC
(In reply to comment #2 from Petr Cerny)
> Created an attachment (id=179222) [details]
> screenshot showing newly selected installed package (from wrong repository)

s/installed/(to be installed)/
Comment 5 Stefan Schubert 2007-11-09 15:59:16 UTC
Please attach a solver testcase.
Comment 6 Petr Cerny 2007-11-12 10:02:14 UTC
(In reply to comment #5 from Stefan Schubert)
> Please attach a solver testcase.

Please, be more specific about what info would you like from me aside from the already attached y2logs and screenshots (when it comes to YaST, I'm a schoolbook example of a total luser).
Comment 8 Stefan Schubert 2007-12-05 11:53:40 UTC
ping ;-)
Comment 9 Petr Cerny 2007-12-06 17:08:19 UTC
Created attachment 186235 [details]
y2logs after selecting -devel package

The resolver now sees, that the package it selcets has different vendor, yet it doesn't see the corresponding package (same vendor and version/release) - see following screenshots
Comment 10 Petr Cerny 2007-12-06 17:09:44 UTC
Created attachment 186237 [details]
screenshot: missing dependencies (wron vendor) warning
Comment 11 Petr Cerny 2007-12-06 17:10:40 UTC
Created attachment 186238 [details]
screenshot: available package versions
Comment 12 Stefan Schubert 2008-04-23 13:20:27 UTC
Will be changed for 11.0 in the selectable.
Comment 13 Michael Andres 2008-04-23 19:40:14 UTC
Maybe not completely. Choosing the right -devel package based on policies affecting its required master package is nothing that can be handled inside the current Selectable.

It's uncertain whether this will change for 11.0.
Comment 14 Michael Andres 2010-08-04 15:01:33 UTC
But canged by using the new satsolver.