Bug 220002

Summary:	Pressing Skip when a package will not load, causes package installation window to shutdown.
Product:	[openSUSE] openSUSE 10.2	Reporter:	Robby Verberne <monkey9>
Component:	YaST2	Assignee:	E-mail List <bnc-team-screening>
Status:	RESOLVED DUPLICATE	QA Contact:	Jiri Srain <jsrain>
Severity:	Major
Priority:	P5 - None	CC:	andreas.hanke
Version:	Beta 1 plus
Target Milestone:	---
Hardware:	64bit
OS:	Other
Whiteboard:
Found By:	Beta-Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Robby Verberne 2006-11-10 18:48:38 UTC

Doing an upgrade to Beta2 from Beta1+.
2 Times fails to download Yast-bootfloppies, and 2 times gpart.
It turns out o be nothing remembered of the choices made for the upgrade.
Counting the allready installed packages allright.
Not able to finish yet, server unaccessible...

M9.

Comment 1 Robby Verberne 2006-11-11 13:47:13 UTC

This morning I wanteed to continue upgrading, nothing seemed the need to be upgraded, after a check, the url:http://ftp-1.gwdg.de/pub/opensuse/distribution/SL-OSS-factory/inst-source
Was vanished from the instalations source catalog!?!
Adding it again was not a problem...

Comment 2 Robby Verberne 2006-11-11 14:00:39 UTC

After getting al the info, and choosing upgrade system, i did not have to enter the choices again, so the yast package, which was installed yesterday, had that fixed.

Comment 3 Robby Verberne 2006-11-11 14:51:46 UTC

Upgrading fantastic until now, y2base consumes nothing at all, between 0.7 7.0 cpu, mem approx. 0.2-13.0 %.
This means all functions can be run without delay.
Speed: 2,5 GB in approx, 2h35min.
Until now, i have never seen Yast2 working this fast, and economic.

Comment 4 Andreas Hanke 2006-11-11 14:56:58 UTC

The problem described in the initial report (Installation stops on a failed package) is _not_ fixed, you just didn't hit a situation where this would have happened on the second attempt.

As the other mentioned problems are already fixed, I consider this a duplicate of bug 217425.

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