Bug 12928

Summary: Upgrade to Mageia3 fails
Product: Mageia Reporter: Bill Hodges <hodges7>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED OLD QA Contact:
Severity: normal    
Priority: Normal CC: olivier
Version: 4   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: Mageia 4 distro CVE:
Status comment:

Description Bill Hodges 2014-03-03 22:55:05 CET
Description of problem:


Mageia 4

How reproducible:Upgrading Mageia 3.
Install produced an error that irqmbalance not unpackable.
Upon install, reboot installation of RPMs using RpmDrake faile with
vendor-perl/5.18.1/Rpmdrake/pkg.pm line 705 uninitialized variable


Steps to Reproduce:
1.update
2.do not install missing rpms

3.reboot, use RPMdrake to update


Reproducible: 

Steps to Reproduce:
Comment 1 Manuel Hiebel 2014-03-06 00:42:19 CET
better if you uninstall it ? (it could be a pkg corruption or something like that)

Component: Installer => RPM Packages

Comment 2 Bill Hodges 2014-03-06 15:59:31 CET
Since upgrade did not work I installed from scratch.
More work, but it was sucessful.
I have another box that I probably will try
the online upgrade since it says in the notes
that upgrade could fail since the machine may have
been upgraded beyond the baseline expected by
the installer?

Bill
Comment 3 Olivier FAURAX 2014-10-22 17:22:59 CEST
On your Mageia4, do you have irqmbalance installed?
Do you still have another box to upgrade?

CC: (none) => olivier

Comment 4 Samuel Verschelde 2015-09-21 13:18: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 5 Marja Van Waes 2015-10-27 06:56:15 CET
As announced over a month ago, 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.

This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version)

If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 
1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED"
2. click on "Version" and change it against that version of Mageia. If you know 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.
3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page:
https://wiki.mageia.org/en/How_to_report_a_bug_properly

If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). 


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/

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