Bug 332175

Summary:	errors during downloading - auto-retry failed download
Product:	[openSUSE] openSUSE 10.3	Reporter:	macias - <bluedzins>
Component:	Installation	Assignee:	Ladislav Slezák <lslezak>
Status:	RESOLVED DUPLICATE	QA Contact:	Jiri Srain <jsrain>
Severity:	Enhancement
Priority:	P5 - None	CC:	locilka
Version:	Final
Target Milestone:	---
Hardware:	i586
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description macias - 2007-10-09 13:34:31 UTC

Currently installation/upgrade is too fragile. I upgraded two computers, one upgrade took me ~3 hours, no errors during downloading, the second upgrade over 6 hours.

Why? Because there were errors during downloading (probably too much traffic to opensuse site), so very often computer displayed error for half an hour when I was busy doing something else.
It is design flaw -- you cannot expect that user would sit straight for 3 hours staring at monitor.

Not mentioning popular install/upgrade during the night. With such solution it won't work because installer could stop after 5 minutes, so after 8 hours of sleep, when user is expecting to see fresh system she/he just would see barely started process.

Comment 1 macias - 2007-10-10 07:56:16 UTC

Hmm, I have a better idea -- auto-retry.

For example, packages to download, A B C D 

A --> ok.
B --> error -> auto-retry set to 10 seconds (user is asleep), after 10 seconds, error -> autoretry in 1 minute ... -> error --> autoretry in 10 minutes ... this time ok
C --> ok
D --> error, autoretry in 10 seconds (and so on)

With such feature installation would be really automatic.

Comment 2 Michal Zugec 2007-10-17 17:18:53 UTC

It's feature for pkg-bindings

Comment 3 Ladislav Slezák 2007-10-18 06:48:02 UTC

Autoretry seems to be a good idea, postponing errors is not possible due to package dependencies (PreRequires).

Comment 4 Ladislav Slezák 2008-03-21 17:19:26 UTC

This seems to be a duplicate of bug #328822

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