Bug 406344

Summary:	Handling changes in the repository during commit
Product:	[openSUSE] openSUSE 10.2	Reporter:	ferdinand gassauer <gassauer>
Component:	libzypp	Assignee:	Duncan Mac-Vicar <dmacvicar>
Status:	RESOLVED DUPLICATE	QA Contact:	Klaus Kämpf <kkaempf>
Severity:	Enhancement
Priority:	P5 - None
Version:	Final
Target Milestone:	---
Hardware:	64bit
OS:	openSUSE 10.3
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description ferdinand gassauer 2008-07-03 22:32:35 UTC

yast2-2.17.2-2.3
BTW
* this version is really much faster in handling a big number of repositories and does not require so much memory.
* what I would like to see is "all updateable files". (blue colored)
* that the RMB function on "All in this List/Update if newer version is available" in a pattern will eventually work one day. (only the Menu Entry -All Packages-Update if newer version is available" wokrs

After selecting update all packages with new versions in KDEBASE Desktop I got the message that some 800 files (packages I assume) will be updated, some 4 GB.
BTW all GNOME files have been included in KDE Base Desktop
BTW it takes many very long minutes (some 30 minutes) to resolve the dependencies - but without any feedback - just 100% CPU usage

During the estimated 5 hours update apparently some files in the repositories have been replaced with newer ones and yast2 update stops asking abort/skip.
So what can the user decide
- abort: results in a partly updated system with the possibility to restart the remaining update, but without rereading the repositories.
- skip: results in a partly updated system
- retry: does not help, because the file does not exist.
- rollback: this option does not exist.

So IMHO yast2 software update should gracefully do, what the user has to do in any case.

users action to get a consistant system.
* exit yast2 software management
* restart yast2 software management - which rereads the repositories - and
* run the "same" update with the reread repositories and hopefully without missing files. the problem is, that the user has to redefine the updates.

BTW I had to skip 170 packages !!!!

Comment 1 ferdinand gassauer 2008-07-15 18:46:02 UTC

Thinking of the number of packages in this update I would say it is likely tha I have selected 
* "Package / All packages" from the top menu instead of 
* "Package / All in this List"

as I reported already frequently "RMB / Update all in this List / if newer versions availabe" does not do any updates.

Comment 3 Klaus Kämpf 2008-09-09 10:24:09 UTC

Rephrased summary.

Since openSUSE 11.0 this issue should be mostly solved

- dependency solving is *much* faster now
- package downloads go through 'openSUSE redirector', which automatically selects a mirror offering the package in question

Still there is a slight chance for out-of-sync operations, esp. in fast changing repos like openSUSE factory. For these scenarios, a 'download all rpms before commit' is probably the best (only?) solution.

Passing to libzypp team for evaluation.

Comment 4 ferdinand gassauer 2008-09-09 12:05:39 UTC

download all rpms before commit ...

and eventually install everything, except the missing packages and dependent packages.

Comment 5 Duncan Mac-Vicar 2008-10-08 11:05:33 UTC

This bug has more than one bug in one, and the download in parallel or before commit is already in other bugs.



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