Bug 396159

Summary:	Downloading package during installation could have a rety count in case of a bad download
Product:	[openSUSE] openSUSE 11.0	Reporter:	Forgotten User CxVz4LpaB5 <forgotten_CxVz4LpaB5>
Component:	Installation	Assignee:	Ladislav Slezák <lslezak>
Status:	RESOLVED DUPLICATE	QA Contact:	Jiri Srain <jsrain>
Severity:	Enhancement
Priority:	P5 - None	CC:	peebhat
Version:	RC 1
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Forgotten User CxVz4LpaB5 2008-05-31 17:14:01 UTC

I have upgraded from beta3 to rc1. during the installation process, the setup ask me which repository I can enable or disable. I have re enable all the one listed. The setup download them the necessary up to date package. During the download, I have a error message:
'Package libgsm1 is broken, integrity check has failed'

I have selected the retry button and this time the installation of the package worked. Maybe the setup can have a 'retry in case something wrong' function and a counter to see if the issue is with the download or the package but not warn the user if the first issue is just a 1-hit download issue.

Comment 2 Ladislav Slezák 2008-06-04 07:44:05 UTC

There already is an automatic retry, but only for IO_SOFT errors (unreachable server or something like that). If the package is broken retrying is not used. That could be probably enhanced...

Comment 3 Peter Poeml 2008-06-10 09:41:01 UTC

A simple retry is prone to get the same non-matching package again. It
would be better to try different mirror (mirrors are involved in the
large majority of use cases), following the suggestion in 
http://en.opensuse.org/Libzypp/Failover. 

Then it could seamlessly work even when half of the mirrors deliver a
wrong/outdated/broken package. (Self-healing downloads...)

Comment 4 Ladislav Slezák 2008-09-29 15:50:50 UTC

*** Bug 403673 has been marked as a duplicate of this bug. ***

Comment 5 Ladislav Slezák 2008-10-14 15:05:56 UTC


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