Bug 14628

Summary: Upgrade from Mageia 3 to 4 fails
Product: Mageia Reporter: Dave Hodgins <davidwhodgins>
Component: RPM PackagesAssignee: Thierry Vignaud <thierry.vignaud>
Status: RESOLVED OLD QA Contact:
Severity: major    
Priority: Normal CC: marja11
Version: 4   
Target Milestone: ---   
Hardware: i586   
OS: Linux   
Whiteboard:
Source RPM: CVE:
Status comment:
Attachments: Log from failed mgaapplet upgrade on an i586 system

Description Dave Hodgins 2014-11-21 01:23:22 CET
During a test of upgrade from Mageia 3 to 4, the upgrade stops due to ...
libmesagl1-10.0.5-1.1.mga4.i586.rpm mesa-1g_module_open() failed for /usr/lib/gdk-pixbuf-2.
0/2.10.0/loaders/libpixbufloader-svg.so: /lib/libgbm.so.1: undefined symbol: wayland_buffer_is_drm

The upgrade does continue after the above message, but later aria2 fails
to download packages that are currently on the selected mirror. I'm not
sure if this is an aria2 problem, or if the mirror was syncing at the
time.

This was a mgaapplet upgrade test on an i586 vb guest.

A urpmi upgrade test on an x86_64 system using my local repo worked fine.

I'm not sure exactly what the problem is. I'll attach the full log


Reproducible: 

Steps to Reproduce:
Comment 1 Dave Hodgins 2014-11-21 01:25:20 CET
Created attachment 5627 [details]
Log from failed mgaapplet upgrade on an i586 system
Dave Hodgins 2014-11-21 01:38:45 CET

Assignee: bugsquad => thierry.vignaud

Comment 2 Dave Hodgins 2014-11-21 01:45:45 CET
Also my dsl connection currently keeps dropping for a few seconds at a time
now, so it may have been a network problem, causing aria2c to fail.
Comment 3 Samuel Verschelde 2015-09-21 13:21:48 CEST
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't 
able to fix it before Mageia 4's end of life. If you are able to reproduce it 
against a later version of Mageia, you are encouraged to click on "Version" and 
change it against that version of Mageia. If it's valid in several versions, 
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/
Comment 4 Marja Van Waes 2015-10-12 11:24:22 CEST
upgrading from Mga3 to Mga4 is no longer supported ;-)

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