Bug 10123 - Upgrade impossible to complete due to JRE 1.6.0 FCS package installed
Summary: Upgrade impossible to complete due to JRE 1.6.0 FCS package installed
Status: RESOLVED WONTFIX
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: 3
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL: https://docs.google.com/file/d/0B0fPg...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-16 13:06 CEST by Michal Ostrowski
Modified: 2013-05-16 22:27 CEST (History)
0 users

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Michal Ostrowski 2013-05-16 13:06:14 CEST
Description of problem:
After starting the upgrade from version 2 to 3 RC, I have encountered an error about some RPM transactions that could not be completed. Thinking this is only a matter of adding other repositories from web mirrors, I have done so. Unfortunately, there was one package I have installed manually, that was breaking the installation process: jre-1.6.0_33-fcs.x86_64. After several upgrade retries, the failed transactions number has been narrowed down to the aforemenetrioned JRE package and kernel packages. After powering down the machine, Mageia has booted successfully on the older kernel. When I have removed the JRE package, the package updated was able to finish installing the kernel RPMs.

Steps to reproduce:
1. Have Mageia 2 installed
2. Install jre-1.6.0_33-fcs.x86_64 package
3. Attempt the upgrade using installation DVD


Reproducible: 

Steps to Reproduce:
Comment 1 claire robinson 2013-05-16 13:38:17 CEST
Speaking on IRC.

The jre-1.6.0_33-fcs.x86_64 is a Fedora package installed onto Mageia 2 so likely not alot we can do about the errors.
Comment 2 Manuel Hiebel 2013-05-16 22:27:54 CEST
your report.bug is useless at it is from mga2, but yes likely a cantfix/wontfix bug (but I will add a note in the errata.)

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


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