Description of problem: When encountering trouble with downloading a package, the installer asks the user whether to skip or cancel installation. Temporary connectivity problems are expected, but sometimes undetected until the message appears. The expected behaviour is to add a "retry" option to the dialog. Version-Release number of selected component (if applicable): Mageia 2 all-nonfree.img How reproducible: At least once Steps to Reproduce: 1. Start network installation. 2. Begin installing packages. 3. Pull network cable.
and what do you suggest ? provide also the file /root/drakx/report.bug.gz as an attachment if you have one
Sorry, no report.bug.gz The installer stops when the package download fails. The user has to notice it and figures out something is wrong with the network. The user fixes the network and wants to retry downloading the package. I suggest adding a "retry" button.
You didn't got a popup offering you to retry?
Keywords: (none) => NEEDINFOCC: (none) => thierry.vignaud
@rh : Can you give a respons to comment 3 otherwise we have to close this bug. Roelof
CC: (none) => r.wobben
Sorry, I forgot about answering. No, I didn't get a retry popup. The popup I got asked me whether to skip the package or to cancel installation.
The bug is still present in Mageia 3 beta 4.
Created attachment 3675 [details] Installation message The installation was an upgrade of Beta 2, possible that internet connection went down for a few seconds.
Typo: the screenshot comes from Mageia 3 Beta 4
(In reply to rh hn from comment #7) > Created attachment 3675 [details] > Installation message > > The installation was an upgrade of Beta 2, possible that internet connection > went down for a few seconds. No, while you were installing version lib64kms1-2.4.42-1 was replaced on the mirror by lib64kms1-2.4.43-1.mga3.x86_64.rpm (from libdrm-2.4.43-1.mga3.src.rpm) that was committed yesterday at 12:33h by tmb That happens a lot while doing a network cauldron install. There is probably a better way to deal with this than what I do: continuing installation as far as possible and then using the boot.iso to do an upgrade install (again) @ tv what is the proper way to update the urpmi database while installing?
Keywords: NEEDINFO => (none)CC: (none) => marja11Version: 2 => CauldronWhiteboard: (none) => 3beta4
of course the package was pushed instead :-/
As marja11 described in #c9 this can easily happen in an install/upgrade to Cauldron when a package is replaced by the next version. But this won't happen in a released version, since any update will go to the update repo. and not to the release repo. Therefor, although a good report, I close it as wontfix, because it won't appear in a released version. Anyone who disagrees is free to reopen the BR.
Am low in coffee
Status: NEW => RESOLVEDResolution: (none) => WONTFIX