Bug 350521

Summary:	SUSE updater will not use all resolveables, returns error and refuses to complete update
Product:	[openSUSE] openSUSE 10.3	Reporter:	andrew spackman <kiwilinux>
Component:	libzypp	Assignee:	Duncan Mac-Vicar <dmacvicar>
Status:	RESOLVED DUPLICATE	QA Contact:	Duncan Mac-Vicar <dmacvicar>
Severity:	Normal
Priority:	P5 - None	CC:	kiwilinux, schubi, tgoettlicher
Version:	Final
Target Milestone:	---
Hardware:	x86-64
OS:	openSUSE 10.3
Whiteboard:
Found By:	Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description andrew spackman 2007-12-22 18:01:22 UTC

When multiple repositories are used the situation of a package being available in more than one repository can arise. When SUSE updater is used it will not allow an update to proceed if the update is available from a different repository to the one used for the current installed version of the package, even though it is listed as an available optional update. Instead an error is generated and the update process stops. Other updates in the list that would have proceeded without error are skipped when this happens. 
If this same update is requested through YaST software Management the user has an option to continue the update using a different vendor and the update will be done without error.
Is it possible to have an option on the updater that it will automatically accept a change of vendor for a package, to stop this error and the requirement to manually invoke the update through YaST Software Management?

Comment 1 Duncan Mac-Vicar 2008-01-29 10:12:30 UTC

No, automatic vendor jump is not acceptable.

The bug is to stop the other updates because this. Thomas, Stefan, any idea on how could we improve this?

Comment 2 Thomas Göttlicher 2008-01-29 10:33:02 UTC

This sounds not like a technical issue but a workflow definition for this scenario is needed. 

As opensuseupdater is meant as a light weight applet it is not possible to cover everything.

My proposal: When zypper runs into this problem it should exit with an error that tells opensuseupdater that YaST Software Management is needed to continue. In this case opensuseupdater could offer a button to start YaST directly.

Comment 3 Jan Kupec 2008-01-29 17:16:12 UTC

Generaly, if a solver problem occurs. The updater will be able to recognize this situation once the xml output will be implemented (i'll continue to work on it starting tommorow). The prompt for choosing a solution will be uniquely identified.

I agree with Thomas, that the applet should not offer a GUI to resolve the dependency problems. Suggestion to run YaST should be enough.

Comment 4 Jan Kupec 2008-01-29 17:19:11 UTC

Bug 345870 is related, if not a duplicate.

Comment 5 andrew spackman 2008-02-01 19:05:59 UTC

Speaking personally as an end user I am happy to be directed to YaST and i can work out what to do. But I have a few friends that I have encouraged to use OpenSUSE (and they are now) who are not so 'technically' minded. If the solution presented to them is not simple and foolproof they simply will not cope with messing around in YaST. I'm hopeful that your solution will be geared to be able to work for them also. 
I think OpenSUSE is great, keep up the good work.

Comment 6 Duncan Mac-Vicar 2008-02-14 23:37:02 UTC


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