Hello community, here is the log from the commit of package java-1_9_0-openjdk for openSUSE:Factory checked in at 2015-06-10 09:15:48 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/java-1_9_0-openjdk (Old) and /work/SRC/openSUSE:Factory/.java-1_9_0-openjdk.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "java-1_9_0-openjdk" Changes: -------- --- /work/SRC/openSUSE:Factory/java-1_9_0-openjdk/java-1_9_0-openjdk.changes 2015-06-03 08:33:42.000000000 +0200 +++ /work/SRC/openSUSE:Factory/.java-1_9_0-openjdk.new/java-1_9_0-openjdk.changes 2015-06-10 09:15:52.000000000 +0200 @@ -1,0 +2,8 @@ +Mon Jun 8 12:24:25 UTC 2015 - fst...@suse.com + +- Upgrade to upstream tag jdk9-b67 +- Added patch: + * aarch64.patch + - fix build on aarch64 architecture + +------------------------------------------------------------------- Old: ---- 1232f4013417.tar.bz2 197e94e0dacd.tar.bz2 44ee68f7dbac.tar.bz2 4fbcca8ab812.tar.bz2 9dd95cff9dae.tar.bz2 d5963ccce28d.tar.bz2 dc6e8336f51b.tar.bz2 fd6bda430d96.tar.bz2 New: ---- 1abd45df5480.tar.bz2 4418697e56f1.tar.bz2 78c2685daaba.tar.bz2 aarch64.patch c9785bc8ade9.tar.bz2 d47dfabd16d4.tar.bz2 f546760134eb.tar.bz2 f822b749821e.tar.bz2 fd782cd69b04.tar.bz2 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ java-1_9_0-openjdk.spec ++++++ --- /var/tmp/diff_new_pack.uXQd3V/_old 2015-06-10 09:15:54.000000000 +0200 +++ /var/tmp/diff_new_pack.uXQd3V/_new 2015-06-10 09:15:54.000000000 +0200 @@ -33,17 +33,17 @@ %global minorver 9 %global microver 0 %global updatever 0 -%global buildver b66 +%global buildver b67 %global root_project jdk9 %global root_repository jdk9 -%global root_revision dc6e8336f51b -%global corba_revision 44ee68f7dbac -%global hotspot_revision 197e94e0dacd -%global jaxp_revision d5963ccce28d -%global jaxws_revision 1232f4013417 -%global jdk_revision 4fbcca8ab812 -%global langtools_revision fd6bda430d96 -%global nashorn_revision 9dd95cff9dae +%global root_revision f546760134eb +%global corba_revision 4418697e56f1 +%global hotspot_revision d47dfabd16d4 +%global jaxp_revision 78c2685daaba +%global jaxws_revision c9785bc8ade9 +%global jdk_revision 1abd45df5480 +%global langtools_revision fd782cd69b04 +%global nashorn_revision f822b749821e %global icedtea_sound_version 1.0.1 # priority must be 6 digits in total %global priority %(echo "10000 * %{majorver} + 1000 * %{minorver} + 100 * %{microver} + %{updatever}" | bc) @@ -216,6 +216,8 @@ Patch101: s390-size_t.patch # Patch for PPC/PPC64 Patch103: ppc-zero-hotspot.patch +# Patch for AARCH64 +Patch104: aarch64.patch # Patches for system libraries Patch203: fix-system-jpeg-loading.patch Patch204: giflib.patch @@ -500,6 +502,10 @@ %patch103 -p1 %endif +%ifarch %aarch64 +%patch104 -p1 +%endif + %patch500 -p1 # Extract systemtap tapsets @@ -939,7 +945,6 @@ --slave %{_bindir}/jstack jstack %{sdkbindir}/jstack \ --slave %{_bindir}/jstat jstat %{sdkbindir}/jstat \ --slave %{_bindir}/jstatd jstatd %{sdkbindir}/jstatd \ - --slave %{_bindir}/native2ascii native2ascii %{sdkbindir}/native2ascii \ --slave %{_bindir}/rmic rmic %{sdkbindir}/rmic \ --slave %{_bindir}/schemagen schemagen %{sdkbindir}/schemagen \ --slave %{_bindir}/serialver serialver %{sdkbindir}/serialver \ @@ -986,8 +991,6 @@ %{_mandir}/man1/jstat-%{sdklnk}.1$ext \ --slave %{_mandir}/man1/jstatd.1$ext jstatd.1$ext \ %{_mandir}/man1/jstatd-%{sdklnk}.1$ext \ - --slave %{_mandir}/man1/native2ascii.1$ext native2ascii.1$ext \ - %{_mandir}/man1/native2ascii-%{sdklnk}.1$ext \ --slave %{_mandir}/man1/rmic.1$ext rmic.1$ext \ %{_mandir}/man1/rmic-%{sdklnk}.1$ext \ --slave %{_mandir}/man1/schemagen.1$ext schemagen.1$ext \ @@ -1116,7 +1119,6 @@ %{_mandir}/man1/jstack-%{sdklnk}.1* %{_mandir}/man1/jstat-%{sdklnk}.1* %{_mandir}/man1/jstatd-%{sdklnk}.1* -%{_mandir}/man1/native2ascii-%{sdklnk}.1* %{_mandir}/man1/rmic-%{sdklnk}.1* %{_mandir}/man1/schemagen-%{sdklnk}.1* %{_mandir}/man1/serialver-%{sdklnk}.1* ++++++ 1232f4013417.tar.bz2 -> 1abd45df5480.tar.bz2 ++++++ /work/SRC/openSUSE:Factory/java-1_9_0-openjdk/1232f4013417.tar.bz2 /work/SRC/openSUSE:Factory/.java-1_9_0-openjdk.new/1abd45df5480.tar.bz2 differ: char 11, line 1 ++++++ 44ee68f7dbac.tar.bz2 -> 4418697e56f1.tar.bz2 ++++++ diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/corba-44ee68f7dbac/.hg_archival.txt new/corba-4418697e56f1/.hg_archival.txt --- old/corba-44ee68f7dbac/.hg_archival.txt 2015-05-21 19:07:35.000000000 +0200 +++ new/corba-4418697e56f1/.hg_archival.txt 2015-05-29 01:50:28.000000000 +0200 @@ -1,4 +1,4 @@ repo: 55540e827aef970ecc010b7e06b912d991c8e3ce -node: 44ee68f7dbacab24a45115fd6a8ccdc7eb6e8f0b +node: 4418697e56f1f43597f55c7cb6573549c6117868 branch: default -tag: jdk9-b66 +tag: jdk9-b67 diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/corba-44ee68f7dbac/.hgtags new/corba-4418697e56f1/.hgtags --- old/corba-44ee68f7dbac/.hgtags 2015-05-21 19:07:35.000000000 +0200 +++ new/corba-4418697e56f1/.hgtags 2015-05-29 01:50:28.000000000 +0200 @@ -308,3 +308,4 @@ 0acac6937de7a0868f8c6f88b7d036d780abeee6 jdk9-b63 0a5e5a7c3539e8bde73d9fe55750e49a49cb8dac jdk9-b64 afc1e295c4bf83f9a5dd539c29914edd4a754a3f jdk9-b65 +44ee68f7dbacab24a45115fd6a8ccdc7eb6e8f0b jdk9-b66 diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/corba-44ee68f7dbac/src/java.corba/share/classes/org/omg/DynamicAny/package.html new/corba-4418697e56f1/src/java.corba/share/classes/org/omg/DynamicAny/package.html --- old/corba-44ee68f7dbac/src/java.corba/share/classes/org/omg/DynamicAny/package.html 2015-05-21 19:07:35.000000000 +0200 +++ new/corba-4418697e56f1/src/java.corba/share/classes/org/omg/DynamicAny/package.html 2015-05-29 01:50:28.000000000 +0200 @@ -25,7 +25,7 @@ Please contact Oracle, 500 Oracle Parkway, Redwood Shores, CA 94065 USA or visit www.oracle.com if you need additional information or have any questions. - + --> </head> @@ -40,97 +40,97 @@ been compiled with the object implementation). As a result, the object receiving the <code>any</code> does not have a portable method of using it. -<P><code>DynAny</code>s enable traversal of the data value associated with an -<code>any</code> at runtime, and extraction of the primitive constituents of the data value. -This is especially helpful for writing powerful generic servers (bridges, event channels -supporting filtering). Similarly, this facility enables the construction of an -<code>any</code> at runtime, without having static knowledge of its type. This is especially +<P><code>DynAny</code>s enable traversal of the data value associated with an +<code>any</code> at runtime, and extraction of the primitive constituents of the data value. +This is especially helpful for writing powerful generic servers (bridges, event channels +supporting filtering). Similarly, this facility enables the construction of an +<code>any</code> at runtime, without having static knowledge of its type. This is especially helpful for writing generic clients (bridges, browsers, debuggers, user interface tools). -<P><code>Any</code> values can be dynamically interpreted (traversed) and constructed through -<tt>DynAny</tt> objects. A <tt>DynAny</tt> object is associated with a data -value which corresponds to a copy of the value inserted into an <tt>Any</tt>. A +<P><code>Any</code> values can be dynamically interpreted (traversed) and constructed through +<tt>DynAny</tt> objects. A <tt>DynAny</tt> object is associated with a data +value which corresponds to a copy of the value inserted into an <tt>Any</tt>. A <tt>DynAny</tt> object may be viewed as an ordered collection of component -<tt>DynAny</tt>s. For <tt>DynAny</tt>s representing a basic type, such as <code>long</code>, -or a type without components, such as an empty exception, the ordered collection of -components is empty. - -<P>Each <tt>DynAny</tt> object maintains the notion of a current position into its collection -of component <tt>DynAny</tt>s. The current position is identified by an index value that runs -from 0 to n-1, where <em>n</em> is the number of components. The special index value -1 +<tt>DynAny</tt>s. For <tt>DynAny</tt>s representing a basic type, such as <code>long</code>, +or a type without components, such as an empty exception, the ordered collection of +components is empty. + +<P>Each <tt>DynAny</tt> object maintains the notion of a current position into its collection +of component <tt>DynAny</tt>s. The current position is identified by an index value that runs +from 0 to n-1, where <em>n</em> is the number of components. The special index value -1 indicates a current position that points nowhere. For values that cannot have a current position (such as an empty exception), the index value is fixed at -1. - If a <code>DynAny</code> is initialized with a value that has components, the index is + If a <code>DynAny</code> is initialized with a value that has components, the index is initialized to 0. - After creation of an uninitialized <code>DynAny</code> (that is, a <code>DynAny</code> that + After creation of an uninitialized <code>DynAny</code> (that is, a <code>DynAny</code> that has no value but a <code>TypeCode</code> that permits components), the current position depends on the type of value represented by - the <code>DynAny</code>. (The current position is set to 0 or -1, depending on whether the + the <code>DynAny</code>. (The current position is set to 0 or -1, depending on whether the new <code>DynAny</code> gets default values for its components.) - - - <P>The iteration operations <code>rewind</code>, <code>seek</code>, and <code>next</code> + + +<P>The iteration operations <code>rewind</code>, <code>seek</code>, and <code>next</code> can be used to change the current position - and the <code>current_component</code> operation returns the component at the current + and the <code>current_component</code> operation returns the component at the current position. - The <code>component_count</code> operation returns the number of components of a + The <code>component_count</code> operation returns the number of components of a <code>DynAny</code>. - Collectively, these operations enable iteration over the components of a + Collectively, these operations enable iteration over the components of a <code>DynAny</code>, for example, to (recursively) examine its contents. - <P>A constructed <code>DynAny</code> object is a <code>DynAny</code> object associated with + <P>A constructed <code>DynAny</code> object is a <code>DynAny</code> object associated with a constructed type. - There is a different interface, inheriting from the <code>DynAny</code> interface, + There is a different interface, inheriting from the <code>DynAny</code> interface, associated with each kind of constructed type in IDL (fixed, enum, struct, sequence, union, array, - exception, and value type). A constructed <code>DynAny</code> object exports operations + exception, and value type). A constructed <code>DynAny</code> object exports operations that enable the creation of new <code>DynAny</code> objects, each of them associated with a component of the constructed data value. - As an example, a <code>DynStruct</code> is associated with a <code>struct</code> value. This + As an example, a <code>DynStruct</code> is associated with a <code>struct</code> value. This means that the <code>DynStruct</code> may be seen as owning an ordered collection of components, one for each structure member. - The <code>DynStruct</code> object exports operations that enable the creation of new + The <code>DynStruct</code> object exports operations that enable the creation of new <code>DynAny</code> objects, each of them associated with a member of the <code>struct</code>. - - - <P>If a <code>DynAny</code> object has been obtained from another (constructed) + + +<P>If a <code>DynAny</code> object has been obtained from another (constructed) <code>DynAny</code> object, - such as a <code>DynAny</code> representing a structure member that was created from a + such as a <code>DynAny</code> representing a structure member that was created from a <code>DynStruct</code>, the member <code>DynAny</code> is logically contained in the <code>DynStruct</code>. - Calling an <code>insert</code> or <code>get</code> operation leaves the current position + Calling an <code>insert</code> or <code>get</code> operation leaves the current position unchanged. - Destroying a top-level <code>DynAny</code> object (one that was not obtained as a component + Destroying a top-level <code>DynAny</code> object (one that was not obtained as a component of another <code>DynAny</code>) also destroys any component <code>DynAny</code> objects obtained from it. Destroying a non-top level <code>DynAny</code> object does nothing. - Invoking operations on a destroyed top-level <code>DynAny</code> or any of its descendants + Invoking operations on a destroyed top-level <code>DynAny</code> or any of its descendants raises OBJECT_NOT_EXIST. - If the programmer wants to destroy a <code>DynAny</code> object but still wants to + If the programmer wants to destroy a <code>DynAny</code> object but still wants to manipulate some component - of the data value associated with it, then he or she should first create a + of the data value associated with it, then he or she should first create a <code>DynAny</code> for the component and, after that, make a copy of the created <code>DynAny</code> object. - - - <P>The behavior of <code>DynAny</code> objects has been defined in order to enable efficient + + +<P>The behavior of <code>DynAny</code> objects has been defined in order to enable efficient implementations - in terms of allocated memory space and speed of access. <code>DynAny</code> objects are +in terms of allocated memory space and speed of access. <code>DynAny</code> objects are intended to be used - for traversing values extracted from <code>any</code>s or constructing values of +for traversing values extracted from <code>any</code>s or constructing values of <code>any</code>s at runtime. - Their use for other purposes is not recommended. - - - +Their use for other purposes is not recommended. + + + <H2>Handling DynAny objects</H2> - - <P><code>Insert</code> and <code>get</code> operations are necessary to handle basic + +<P><code>Insert</code> and <code>get</code> operations are necessary to handle basic <code>DynAny</code> objects but are also helpful to handle constructed <code>DynAny</code> objects. Inserting a basic data type value into a constructed <code>DynAny</code> object @@ -145,9 +145,8 @@ the <code>TypeCode</code> contained in the <code>DynAny</code> or, if the <code>DynAny</code> has components, is equivalent to the <code>TypeCode</code> of the <code>DynAny</code> at the current position. - + <P>Basic operations include: - <P> <UL> <LI>insert_boolean, get_boolean <LI>insert_char, get_char @@ -181,28 +180,28 @@ <LI>get_boxed_value <LI>get_boxed_value_as_dyn_any </UL> - - - <P><code>DynAny</code> and <code>DynAnyFactory</code> objects are intended to be local to + + + <P><code>DynAny</code> and <code>DynAnyFactory</code> objects are intended to be local to the process in which they are - created and used. This means that references to <code>DynAny</code> and + created and used. This means that references to <code>DynAny</code> and <code>DynAnyFactory</code> objects cannot be exported to other processes, or externalized with <code>ORB.object_to_string()</code>. - If any attempt is made to do so, the offending operation will raise a MARSHAL system + If any attempt is made to do so, the offending operation will raise a MARSHAL system exception. - Since their interfaces are specified in IDL, <code>DynAny</code> objects export operations + Since their interfaces are specified in IDL, <code>DynAny</code> objects export operations defined in the standard - <code>org.omg.CORBA.Object</code> interface. However, any attempt to invoke operations + <code>org.omg.CORBA.Object</code> interface. However, any attempt to invoke operations exported through the <code>Object</code> interface may raise the standard NO_IMPLEMENT exception. - An attempt to use a <code>DynAny</code> object with the DII may raise the NO_IMPLEMENT + An attempt to use a <code>DynAny</code> object with the DII may raise the NO_IMPLEMENT exception. <H3>Package Specification</H3> -<P>For a precise list of supported sections of official specifications with which -the Java[tm] Platform, Standard Edition 6 ORB complies, see <A -HREF="../CORBA/doc-files/compliance.html">Official Specifications for CORBA +<P>For a precise list of supported sections of official specifications with which +the Java[tm] Platform, Standard Edition 6 ORB complies, see <A +HREF="../CORBA/doc-files/compliance.html">Official Specifications for CORBA support in Java[tm] SE 6</A>. @since 1.4 ++++++ 1232f4013417.tar.bz2 -> 78c2685daaba.tar.bz2 ++++++ ++++ 1264437 lines of diff (skipped) ++++++ aarch64.patch ++++++ --- jdk9/hotspot/agent/src/os/linux/libproc.h 2015-06-09 08:42:38.197240217 +0200 +++ jdk9/hotspot/agent/src/os/linux/libproc.h 2015-06-09 08:43:43.159810821 +0200 @@ -71,9 +71,6 @@ #if defined(sparc) || defined(sparcv9) || defined(ppc64) #define user_regs_struct pt_regs #endif -#if defined(aarch64) -#define user_regs_struct user_pt_regs -#endif // This C bool type must be int for compatibility with Linux calls and // it would be a mistake to equivalence it to C++ bool on many platforms ++++++ 1232f4013417.tar.bz2 -> c9785bc8ade9.tar.bz2 ++++++ diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/jaxws-1232f4013417/.hg_archival.txt new/jaxws-c9785bc8ade9/.hg_archival.txt --- old/jaxws-1232f4013417/.hg_archival.txt 2015-05-21 19:07:37.000000000 +0200 +++ new/jaxws-c9785bc8ade9/.hg_archival.txt 2015-05-29 01:13:52.000000000 +0200 @@ -1,4 +1,4 @@ repo: 0961a4a211765fea071b8dac419003ee0c3d5973 -node: 1232f4013417e4a9cd291096798d10f2e601d69d +node: c9785bc8ade98a16a050d7520b70c68363857e00 branch: default -tag: jdk9-b66 +tag: jdk9-b67 diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/jaxws-1232f4013417/.hgtags new/jaxws-c9785bc8ade9/.hgtags --- old/jaxws-1232f4013417/.hgtags 2015-05-21 19:07:37.000000000 +0200 +++ new/jaxws-c9785bc8ade9/.hgtags 2015-05-29 01:13:52.000000000 +0200 @@ -311,3 +311,4 @@ b5c22d09b1c91dd49b006f38d8ba9c4397517ccc jdk9-b63 df100399ed27d0eaa57c137ca99819a0fee66178 jdk9-b64 45ef73bb85c12ec1b291835c1d40e342a454e3f0 jdk9-b65 +1232f4013417e4a9cd291096798d10f2e601d69d jdk9-b66 ++++++ 1232f4013417.tar.bz2 -> d47dfabd16d4.tar.bz2 ++++++ /work/SRC/openSUSE:Factory/java-1_9_0-openjdk/1232f4013417.tar.bz2 /work/SRC/openSUSE:Factory/.java-1_9_0-openjdk.new/d47dfabd16d4.tar.bz2 differ: char 11, line 1 ++++++ 1232f4013417.tar.bz2 -> f546760134eb.tar.bz2 ++++++ ++++ 704643 lines of diff (skipped) ++++++ 1232f4013417.tar.bz2 -> f822b749821e.tar.bz2 ++++++ ++++ 988441 lines of diff (skipped) ++++++ 1232f4013417.tar.bz2 -> fd782cd69b04.tar.bz2 ++++++ ++++ 1191237 lines of diff (skipped)