keep java-common pointing to OpenJDK in -proposed

[Matthias Klose]

keep java-common pointing to OpenJDK 10 in -proposed.

[Matthias Klose (doko)]

octave 4.2.2-1build1.1 is built using OpenJDK 10, and should only migrate with the java-common package.

[Steve Langasek (vorlon)]

why does it matter that octave was built against openjdk-10? this really doesn't look like a valid reason to hold the package back.

[Matthias Klose (doko)]

because it records the jvm path in it's packaged files, and as a result octave-io would fail it's autopkg tests in the release pocket.

[Matthias Klose (doko)]

yes, these tests are failing in proposed as well, but the reason here is some incompatibility with OpenJDK 10

[Steve Langasek (vorlon)]

is this only a test failure in octave-io, or is something here RC-buggy for hard-coding a path to the jvm without declaring a dependency?

[Mike Miller (mtmiller)]

So octave 4.2.2-1build1.1 actually failed to detect java and disabled it completely, looking at the build logs. I think you want to include the attached patch, it should let octave build with java 10 or 11, whichever you land on for bionic.

[Ubuntu Foundations Team Bug Bot (crichton)]

The attachment "octave-configure-java11.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

[Steve Langasek (vorlon)]

Both packages now ready to migrate except for this blocking bug; closing.