Mageia forum

I used the Netinstall iso, boot-nonfree.iso amd64 of 12th April, notebook Vaio E Series SVE1713G4EW mit Win 8 und UEFI.

My choices were
- Language: English, secondary Languages German, brazilian Portuguese
- Filesystem btrfs, custom partitioning
- Desktop KDE

I ran into a popup windows as follows

Code: Select all

An error occurred:

ERROR: 'script' failed for x11-server-common-1.18.3-5.mga6
ERROR: 'script' failed fpr memtest86+-5.01-9.mga6


Acknowledged with Button [OK]

Next windows

Code: Select all

13 Installation transactions failed


Acknowledged with Button [OK]

Next window is Details window with Buttons [Release notes], [Cancel], [No Details], pressed [Cancel].
The Installer returns to the Media Selection page, where is only a button [Next].
The installation process thus loops infinitely. No chance to abort. I had to switch off with the power button of my notebook.

Did I oversee something, or should I write a bug report: It should be possible to abort, and perhaps a hint, that the installation can be retaken later without formatting.

Best regards,
Bequimão

The network installer was never designed to handle a Cauldron installation and probably never will be.

What happens is that a list of packages along with their version is fetched from the release repositories to be installed.
This works for a stable release as those repositories never change but with Cauldron updates get pushed to the release repositories replacing the older versions that the installer is looking for and the installation fails.

Ken-Bergen wrote:The network installer was never designed to handle a Cauldron installation and probably never will be.

Hmmm? network installer was designed to directly pull the packages from mirror. If you have a mirror that doesn't sync as frequently and is consistent during installation, this usually works just fine.

doktor5000 wrote:Hmmm? network installer was designed to directly pull the packages from mirror. If you have a mirror that doesn't sync as frequently and is consistent during installation, this usually works just fine.

Yes, if the stars stay in alignment it works, if they shift it fails and you start over.

Yep, but isn't that basically what all of cauldron is about?

In any case, usually I do the install via the dual arch DVD, replace urpmi repos and then simply run urpmi --auto-update --auto until all packages have been updated, and reboot to my new cauldron install.

Hi,

I took the netinstall iso, because the Mageia 6 dev 1 did not work on my system. Now I do have a workaround.
https://bugs.mageia.org/show_bug.cgi?id=18111

Even Mageia packagers may commit errors. So the issue can repeat itself in the stable branch. A poor error handling is the hallmark of bad programmers. I would distrust a distribution as a whole, if I ran into such error (in a stable version). So I will write a bug report.

Kind regards,
Bequimão

Edit: https://bugs.mageia.org/show_bug.cgi?id=18215

Bequimao wrote:So I will write a bug report.

Yep, that would be appreciated - if the error is reproducible.

I tried the network installer and had similar problems as well. Basically the same problem. but from a different perspective.

Apart from the changing repository which is the nature of cauldron after all, I found that the installer insists on installing chromium and flash even if you deselect them in individual package selection and if a package is not present the installer will enter an endless loop of getting you back to package and DE selection.

I don't know if this is by design to counter the changing nature of cauldron repository, but with previous (stable) installations if a package was not present (for example not present in local repository) you could still complete the installation. I am talking about packages like some graphics program or flash and not vital system components.

Trying to finish the installation I got into a situation where I didn't have the option to set root and user credentials, which required several attempts of reinstallation. (I know I could enter the shell from grub but it doesn't seem to work this way with grub2)