Bug 27185 - Upgrade from MGA6 to MGA8beta1 32bit script crash
Summary: Upgrade from MGA6 to MGA8beta1 32bit script crash
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-08-23 21:09 CEST by Joe Da Silva
Modified: 2020-08-23 21:24 CEST (History)
0 users

See Also:
Source RPM:
CVE:
Status comment:


Attachments
initial 'script' error - Upgrade from MGA6 to MGA8-beta1 (8.38 KB, image/jpeg)
2020-08-23 21:12 CEST, Joe Da Silva
Details
list of 36 packages failed ot install (38.12 KB, image/jpeg)
2020-08-23 21:17 CEST, Joe Da Silva
Details

Description Joe Da Silva 2020-08-23 21:09:38 CEST
Description of problem:
'script' failed for perl-XML-LibXML-2.20.500-3.mga.i586
'script' failed for perl-LibXML-2.13.200-1.1.mga6.i586

Version-Release number of selected component (if applicable): 8beta1 (32bit) classic

How reproducible: unknown (only tried once - no backups used - plan was to fresh install - but decided to see what happened on upgrading).

Steps to Reproduce:
1. existing MGA6.i586 on SSD
2. create MGA8.i586 classic on USB stick
3. boot from USB for install, begin upgrade.
Comment 1 Joe Da Silva 2020-08-23 21:12:05 CEST
Created attachment 11823 [details]
initial 'script' error - Upgrade from MGA6 to MGA8-beta1

kept file size down to  'small' 9k file
Comment 2 Joe Da Silva 2020-08-23 21:17:40 CEST
Created attachment 11824 [details]
list of 36 packages failed ot install

If this helps - great - if not - that's okay too.
Comment 3 Aurelien Oudelet 2020-08-23 21:20:30 CEST
Hi, thanks reporting this but so sorry,

This is not supported way to do system upgrade.

Supported way is upgrade from Mageia 6 to 7 (and after from 7 to 8 Beta 1).


Closing this INVALID.

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

Comment 4 Joe Da Silva 2020-08-23 21:24:42 CEST
Thanks for the very quick reply. closed is fine.
I wasn't expecting too much on the bug as it seemed far-fetched.

Keep-up the great distro - Thanks :-)

Note You need to log in before you can comment on or make changes to this bug.