Bug 1131

Summary:	With network installation, you can't change server if there is an issue during download.
Product:	Mageia	Reporter:	Pierre Bonneau <pmithrandir>
Component:	Installer	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	enhancement
Priority:	Normal	CC:	marja11
Version:	Cauldron
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:	drakx-installer-stage2	CVE:
Status comment:

Description Pierre Bonneau 2011-05-04 12:09:46 CEST

Description of problem:
I launched my installation with a boot.iso usb key.
After that, I type linux to install it, and after few question, the installer asked me to choose a server.

The installation started well(with graphical interface), but during it, I got 2 problems with the same result.

First : 
The installer said it didn't fond the non-free repositorie.

Second : 
During download, I got some error during download

When either of them happen, you can't ask to the installer to retry.
You can't either ask him to choose an alternative server to download these packages.

So after half an hour of download, or even with just one package lost, you can't finish your installation properly, and you have to download everything again.

Version-Release number of selected component (if applicable):
Cauldron beta 2

Ahmad Samir 2011-05-04 23:43:57 CEST

Summary: with boot.iso installation, you can't change server if there is an issue during download. => With network installation, you can't change server if there is an issue during download.
Source RPM: (none) => drakx-installer-stage2
Severity: normal => enhancement

Comment 1 Marja Van Waes 2011-10-12 19:38:57 CEST

@ Pierre

Sorry for replying so late.

Do you, by any chance, know what this was like during Mageia 1 install. Was the problem still there?

CC: (none) => marja11

Comment 2 Pierre Bonneau 2011-10-12 21:04:14 CEST

Sorry, no idea. I didn't try anymore after that.

Comment 3 Marja Van Waes 2011-10-12 21:31:27 CEST

@ Pierre

Thanks for replying.

Closing as "old" because this issue wasn't confirmed in a release that is still supported

Status: NEW => RESOLVED
Resolution: (none) => OLD