Product: Mageia 2 beta 3 64-bit DVD My attempt to upgrade Mageia 1 to 2 beta 3 failed at the "Package Selection" stage on my 64-bit Samsung X360 laptop. The installer booted as expected, with normal results and arrived at the screen offering the choice of a new install or an upgrade from Mageia 1. Selecting this resulted in the message Attempt to reload Scalar/Util.pm aborted Compilation failed in require. The install log on the Clrt+Alt+F3 (or F4) supplied the additional information Compilation failed in require at /usr/lib/perl5/5/14/2/overload.pm line 97.
Hi, can you also provide the file /root/drakx/report.tar.gz (even I'm not sure it's useful for upgrade)
Blocks: (none) => 3342Source RPM: (none) => drakx-installer-stage2
Created attachment 2070 [details] Debug log from failed install
That is the only logfile created by the failed upgrade.
Assignee: bugsquad => thierry.vignaud
Comment on attachment 2070 [details] Debug log from failed install you should have attach the one in /tmp in the installer (the one in /mnt/root/drakx/ aka in the chrooted installed system is updated from times to times)
Attachment 2070 is obsolete: 0 => 1
Status: NEW => ASSIGNED
Created attachment 2073 [details] Debug log from second failed upgrade install OK, after a second attempt at the upgrade install with exactly the same results, here is the debug log. To be cleat, this is the ONLY log file in /tmp of the installer.
Should be fixed if you a net update from this morning installer
Status: ASSIGNED => RESOLVEDResolution: (none) => FIXED
Is it OK for you with latest boot.iso?
Created attachment 2099 [details] Debug.log from task-printing failure
The new boot.iso solves that problem and allows the upgrade to proceed to the next point of failure. Urpmi is encountering some failure with the task-printing packages. Does this merit a new bug report?
A new bug report should be opened. Looking at the log, it looks like the first problem is caused by pm-utils which is stopping kdebase4-workspace-4.8.2-5.mga2.x86_64 from getting installed, which in turn causes most of kde and the task packages to fail as well, so I think it should be opened against that package. Instead of uploading the log again, you can refer to it in the new bug report by typing the word attachment followed by the number, 2099 in this case, as in attachment 2009 [details].
CC: (none) => davidwhodgins