Bug 571 - upgrade openjdk 1.6 from b20 to b22 / release number change
Summary: upgrade openjdk 1.6 from b20 to b22 / release number change
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (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: 2011-03-27 17:56 CEST by Y.LE_NY
Modified: 2011-04-09 20:20 CEST (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Y.LE_NY 2011-03-27 17:56:54 CEST
Description of problem:
1)
Mageia 1 Alpha2 use OpenJDK 1.6.0_20 (build 20) release 
but the latest stable version is 1.6.0_22 (build 22).
Please upgrade it from 1.6.0_20 (build 20) (2010-06-16) to 1.6.0_22 (build 22) (2011-02-18) to fix bugs.

Sources :
http://download.java.net/openjdk/jdk6/


2) There is a change numbering in the package name from 
java-1.6.0-openjdk-1.6.0.0-12.b20.2.mga1 to
java-1.6.0-openjdk-1.6.0.0-13.1.9.6.1.mga1.

With this package java-1.6.0-openjdk-1.6.0.0-12.b20.2.mga1, we have :
$ java -version
java version "1.6.0_20"
OpenJDK Runtime Environment (IcedTea6 1.9.5) (12.b20.2.mga1-i386)
OpenJDK Server VM (build 19.0-b09, mixed mode)

With this package java-1.6.0-openjdk-1.6.0.0-13.1.9.6.1.mga1, we have :
$ java -version
java version "1.6.0_20"
OpenJDK Runtime Environment (IcedTea6 1.9.6) (mageia-13.1.9.6.1.mga1-i386)
OpenJDK Server VM (build 19.0-b09, mixed mode)

I think that the package name java-1.6.0-openjdk-1.6.0.0-12.b20.2.mga1 is more explicit because we have the release number (Build xx) for OpenJDK in his name.
For me the release number for IcedTea is less important.

3) There is a securituy update for IcedTea :
http://blog.fuseyism.com/index.php/2011/02/15/security-icedtea6-1710-187-and-197-released/

Version-Release number of selected component (if applicable):
java-1.6.0-openjdk-1.6.0.0-13.1.9.6.1.mga1

Reproducible: 

Steps to Reproduce:
Y.LE_NY 2011-03-27 17:57:01 CEST

CC: (none) => dmorganec

Comment 1 D Morgan 2011-04-07 20:24:00 CEST
fixed on SVN, the new package is on the BS

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

Comment 2 Y.LE_NY 2011-04-09 20:20:51 CEST
Thanks D Morgan

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