Bug 11819

Summary:	Attempted upgrade of M3 using M4B2 Classic Installer results in failure
Product:	Mageia	Reporter:	William Kenney <wilcal.int>
Component:	RPM Packages	Assignee:	Erwan VELU <erwanaliasr1>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	ennael1, thierry.vignaud
Version:	Cauldron
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:	syslinux	CVE:
Status comment:

Description William Kenney 2013-11-29 17:18:50 CET

In VirtualBox, M3, KDE, 32-bit

Package(s) under test:
M3 -> M4B2 upgrade from Classic Installer

I've attempted an upgrade of M3 32-bit KDE to M4B2 using the following media:
Mageia-4-beta2-i586-DVD.iso
md5: 357602aeff9210206ba63600fe8fb9bd

Upgrade almost completed then presented the following message:

1 installation transaction failed

Instalation of packages failed:

File /usr/libsyslinux/mbr.bin from install of
syslinux-6.02-1mga4.i586 conflicts with file from
package extlinux-4.04-5.mga.i586

Proceeding with "OK" resulted in the following message:

An error occured
installation failed

Proceeding with "OK" looks like it loops back on the whole
process and starts all over.

Reproducible: 

Steps to Reproduce:

William Kenney 2013-11-29 17:20:18 CET

Summary: Attempted upgrade of M3 using M4B2 Classic Installer results in Failure => Attempted upgrade of M3 using M4B2 Classic Installer results in failure

Comment 1 Thierry Vignaud 2013-11-30 11:18:09 CET

This is not an installer bug but just a classic packaging issue (lack of versionated conflicts tags when moving files between subpackages)

CC: (none) => ennael1, thierry.vignaud
Component: Installer => RPM Packages
Assignee: bugsquad => erwanaliasr1
Source RPM: (none) => syslinux

Comment 2 Thierry Vignaud 2013-11-30 11:21:33 CET

And why is mbr.bin in syslinux 32 bit package but in extlinux 64bit package????

Comment 3 Thierry Vignaud 2013-11-30 11:35:54 CET

I don't know why mbr.bin is listed in both extlinux & syslinux but for now I just added the proper conflict tags so that they got upgraded in the same transaction, thus fixing that error.

But please check if it's necessary it's listed in both packages.
This is the case since commit rr150075 by erwan on 2011-09-28:
"Updating to 4.04"

Comment 4 William Kenney 2013-12-04 20:03:24 CET

In VirtualBox, M3, KDE, 32-bit

Package(s) under test:
m3 32-bit -> m4b2 32-bit upgrade

I've reattempted an upgrade of M3 32-bit KDE to M4B2 using the following media:
Mageia-4-beta2-i586-DVD.iso
md5: ef77b724cdcc3ed9c1da450ca780e602

This time I was successful. The only wrinkle was that the MCC went missing
from the launch bar at the bottom of the desktop. The MCC operates normally
from the launch menu. I then set up the latest M4B2 repo, updated the now
upgraded M3 -M4B2 and rebooted the system, successfully.

I'm gonna change the Status to Resolved but will retest again as new isos
are published.

Test platform:
Intel Core i7-2600K Sandy Bridge 3.4GHz
GIGABYTE GA-Z68X-UD3-B3 LGA 1155 MoBo
GIGABYTE GV-N440D3-1GI Nvidia GeForce GT 440 (Fermi) 1GB
RTL8111/8168B PCI Express 1Gbit Ethernet
DRAM 16GB (4 x 4GB)
VirtualBox 4.2.16-1.mga3.x86_64.rpm

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