Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.java > #11260 > unrolled thread

OpenJDK 8 watch file

Back to article view | Back to linux.debian.maint.java

Contents

  OpenJDK 8 watch file Martijn Verburg <martijnverburg@gmail.com> - 2019-05-29 12:20 +0200
    Re: OpenJDK 8 watch file Tiago Daitx <tiago.daitx@canonical.com> - 2019-06-05 15:30 +0200

#11260 — OpenJDK 8 watch file

[Multipart message — attachments visible in raw view] — view raw

Hi All,

Starting a new thread here.  I know the Red Hat folks well (AdoptOpenJDK
hosts their OpenJDK binaries for them from the source tarballs as
previously mentioned).

So it sounds like getting the arm sources merged in (or at least kept in
sync) would help?

As an FYI - the 'Official' AArch64 port for OpenjDK 8 (jdk8u) is actually
https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah

I'm not sure if this is where Debian was building from for that platform?

I'll try to chase down arm32/aarch32 - I don't think we're even building
that at Adopt yet ourselves.

-----

OpenJDK 8 is another beast and the openjdk-8 package has to track a
lot more repositories: the "root" openjdk repository, corba, 3 hotspot
repositories (1 for the oracle supported archs, 1 for armhf, another
one for arm64), jaxp, jaxws, jdk, langtools, hotspot, nashorn. And the
arm related hotspot repositories usually lag behind the official one
from a few days to a few months (specially aarch32 used for armhf), so
that can delay the release or require hotspot security patches to be
applied on top of the arm hotspot. That makes having a watch file for
it much harder since the OpenJDK 8 tarballs don't include the code for
the arm hotspots. Hopefully the arm repositories will be eventually
merged upstream now that RedHat is leading OpenJDK 8.

That said, sorry to side track the discussion, if anyone wants to
discuss openjdk-8 further I recommend doing that in a separated
thread. ;-)

------


Cheers,
Martijn

[toc] | [next] | [standalone]

#11267

Hi Martijn,

I somehow missed this email, sorry about that and for the late reply.

On Wed, May 29, 2019 at 7:14 AM Martijn Verburg
<martijnverburg@gmail.com> wrote:
>
> Hi All,
>
> Starting a new thread here.  I know the Red Hat folks well (AdoptOpenJDK hosts their OpenJDK binaries for them from the source tarballs as previously mentioned).
>
> So it sounds like getting the arm sources merged in (or at least kept in sync) would help?

Merging the code would help greatly if the aim is to eventually use
the upstream tarballs.

As for keeping in sync, aarch64 has been doing quite a good work
recently, releasing very closely with upstream.

> As an FYI - the 'Official' AArch64 port for OpenjDK 8 (jdk8u) is actually https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah
>
> I'm not sure if this is where Debian was building from for that platform?

Yes, that's the repository we have been using.

> I'll try to chase down arm32/aarch32 - I don't think we're even building that at Adopt yet ourselves.

It would be great if they could get their releases out faster, similar
to what aarch64 has done - moving from weeks to a couple days or less.
Usually most openjdk-8 packages have been released with an aarch32
hotspot that was 1 or 2 releases behind, with only hotspot security
updates on top (if there's any), thus forsaking any hotspot fixes from
newer releases. Keep in mind that OpenJDK updates in stable
Debian/Ubuntu releases are usually considered security updates, so
this approach is just fine just not optimal. It also allowed us to
provide a faster hotspot for the armhf users, speed up our build, and
being able to run the whole testsuites which was not possible with the
ZeroVM builds.

Regards,
Tiago

>
> -----
>
> OpenJDK 8 is another beast and the openjdk-8 package has to track a
> lot more repositories: the "root" openjdk repository, corba, 3 hotspot
> repositories (1 for the oracle supported archs, 1 for armhf, another
> one for arm64), jaxp, jaxws, jdk, langtools, hotspot, nashorn. And the
> arm related hotspot repositories usually lag behind the official one
> from a few days to a few months (specially aarch32 used for armhf), so
> that can delay the release or require hotspot security patches to be
> applied on top of the arm hotspot. That makes having a watch file for
> it much harder since the OpenJDK 8 tarballs don't include the code for
> the arm hotspots. Hopefully the arm repositories will be eventually
> merged upstream now that RedHat is leading OpenJDK 8.
>
> That said, sorry to side track the discussion, if anyone wants to
> discuss openjdk-8 further I recommend doing that in a separated
> thread. ;-)
>
> ------
>
>
> Cheers,
> Martijn



-- 
Tiago Stürmer Daitx
Software Engineer
tiago.daitx@canonical.com

PGP Key: 4096R/F5B213BE (hkp://keyserver.ubuntu.com)
Fingerprint = 45D0 FE5A 8109 1E91 866E  8CA4 1931 8D5E F5B2 13BE

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.maint.java

csiph-web