Bug#895274: octave and OpenJDK 10

[Tiago Daitx]

On Thu, 19 Apr 2018 18:27:44 -0700 Mike Miller  wrote:
> I posted the attached patch to the Ubuntu bug tracker. This is an
> upstream patch that enables octave configure to detect and build with
> OpenJDK 10 and 11.

Thanks for that!

> I can add this to the octave packaging repo if we expect to have a
> 4.2.2-3 source upload, and if that would be helpful for testing OpenJDK
> transitions.

> We already have 4.4 release candidates (not yet in experimental) and
> expect Octave 4.4 to be stamped in the next week or so, at which point
> the patch won't be needed.

Octave 4.4.0-1 has been uploaded to experimental. I checked debian's build
logs and it seems the build used openjdk-9, so that doesn't tell if fix is
in place.

Just a heads up in case someone else can confirm that the build actually
works with openjdk-10 and then get this closed.

thanks

Bug#895274: octave and OpenJDK 10

[Mike Miller]

On Mon, Apr 09, 2018 at 10:38:52 +0200, Matthias Klose wrote:
> With the recent java-common upload to experimental, octave would need a
> no-change rebuild/upload in experimental to pick up the new defaults.

I posted the attached patch to the Ubuntu bug tracker. This is an
upstream patch that enables octave configure to detect and build with
OpenJDK 10 and 11.

I can add this to the octave packaging repo if we expect to have a
4.2.2-3 source upload, and if that would be helpful for testing OpenJDK
transitions.

We already have 4.4 release candidates (not yet in experimental) and
expect Octave 4.4 to be stamped in the next week or so, at which point
the patch won't be needed.

-- 
mike
Description: configure: Remove characters after java version string
 Fixes configure detection of Java version with OpenJDK 10 and 11, where some
 text appears after the quoted version number.
Author: Rik 
Origin: upstream, https://hg.savannah.gnu.org/hgweb/octave/rev/523298448352
Bug: https://savannah.gnu.org/bugs/?53531
Reviewed-by: Mike Miller 
Last-Update: 2018-04-19
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
--- a/configure.ac
+++ b/configure.ac
@@ -2759,7 +2759,7 @@
 
   ## Check Java version is recent enough.
   AC_MSG_CHECKING([for Java version])
-  java_version=[`"$JAVA" -version 2>&1 | $SED -n -e 's/^[^ ]* version[^0-9"]*"\([^"]*\)"/\1/p'`]
+  java_version=[`"$JAVA" -version 2>&1 | $SED -n -e 's/^[^ ]* version[^0-9"]*"\([^"]*\)".*/\1/p'`]
   AC_MSG_RESULT([$java_version])
   java_major=[`echo $java_version | $SED -e 's/^\([0-9][0-9]*\)\.\([0-9][0-9]*\)\..*$/\1/'`]
   java_minor=[`echo $java_version | $SED -e 's/^\([0-9][0-9]*\)\.\([0-9][0-9]*\)\..*$/\2/'`]


signature.asc
Description: PGP signature

Bug#895274: octave and OpenJDK 10

[Matthias Klose]

Package: src:octave
Version: 4.2.2-2
Severity: important
Tags: sid buster

With the recent java-common upload to experimental, octave would need a
no-change rebuild/upload in experimental to pick up the new defaults.

Even after the rebuild, I see autopkg tests failing for some dependent packages,
currently only seen in Ubuntu (bionic-proposed). These are:

http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#octave

octave-io fails (with the rebuilt octave) with:
http://autopkgtest.ubuntu.com/packages/o/octave-io/bionic/amd64

octave-tisean on amd64
http://autopkgtest.ubuntu.com/packages/o/octave-tisean/bionic/amd64

octave-linear-algebra on s390x
http://autopkgtest.ubuntu.com/packages/o/octave-linear-algebra/bionic/s390x

octave-lfat on arm64
http://autopkgtest.ubuntu.com/packages/o/octave-ltfat/bionic/arm64

I'd appreciate some help getting these passing again.