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


Groups > linux.debian.security > #5800 > unrolled thread

Reintroducing openjdk-8 for Bullseye?

Started byGraham Inggs <ginggs@debian.org>
First post2020-04-09 21:10 +0200
Last post2020-04-09 23:00 +0200
Articles 5 — 4 participants

Back to article view | Back to linux.debian.security


Contents

  Reintroducing openjdk-8 for Bullseye? Graham Inggs <ginggs@debian.org> - 2020-04-09 21:10 +0200
    Re: Reintroducing openjdk-8 for Bullseye? Florian Weimer <fw@deneb.enyo.de> - 2020-04-09 21:20 +0200
      Re: Reintroducing openjdk-8 for Bullseye? Ihor Antonov <ihor@antonovs.family> - 2020-04-09 22:10 +0200
      Re: Reintroducing openjdk-8 for Bullseye? Graham Inggs <ginggs@debian.org> - 2020-04-09 22:30 +0200
        Re: Reintroducing openjdk-8 for Bullseye? Andreas Beckmann <anbe@debian.org> - 2020-04-09 23:00 +0200

#5800 — Reintroducing openjdk-8 for Bullseye?

FromGraham Inggs <ginggs@debian.org>
Date2020-04-09 21:10 +0200
SubjectReintroducing openjdk-8 for Bullseye?
Message-ID<zTKIN-5Lf-1@gated-at.bofh.it>
Dear Security Team

The package nvidia-cuda-toolkit (non-free) ships some Java-based
visual tools; Nvidia Visual Profiler and Nsight Eclipse Edition, which
require the OpenJDK 8 JRE.

When Debian switched default-jre, we started to ship Nvidia's bundled
JRE as nvidia-openjdk-8-jre (see #900300).

As of nvidia-cuda-toolkit 10.1.243, upstream stopped shipping the
bundle JRE, and expect users to download it directly from Oracle.  We
are considering our options, and one which is very attractive for us
is for openjdk-8 to be reintroduced for Bullseye, but the question is
who gets to maintain it?

Please let us know your thoughts.

Regards
Graham

[toc] | [next] | [standalone]


#5801

FromFlorian Weimer <fw@deneb.enyo.de>
Date2020-04-09 21:20 +0200
Message-ID<zTKSt-5Pi-3@gated-at.bofh.it>
In reply to#5800
* Graham Inggs:

> As of nvidia-cuda-toolkit 10.1.243, upstream stopped shipping the
> bundle JRE, and expect users to download it directly from Oracle.  We
> are considering our options, and one which is very attractive for us
> is for openjdk-8 to be reintroduced for Bullseye, but the question is
> who gets to maintain it?

Why did they stop providing the bundled JDK?  Do the AdoptOpenJDK
builds work?  If not, then why would a Debian build of openjdk-8 be
any different?

[toc] | [prev] | [next] | [standalone]


#5802

FromIhor Antonov <ihor@antonovs.family>
Date2020-04-09 22:10 +0200
Message-ID<zTLER-6mG-7@gated-at.bofh.it>
In reply to#5801

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

On Thursday, April 9, 2020 12:11:12 PM PDT Florian Weimer wrote:
> * Graham Inggs:
> > As of nvidia-cuda-toolkit 10.1.243, upstream stopped shipping the
> > bundle JRE, and expect users to download it directly from Oracle.  We
> > are considering our options, and one which is very attractive for us
> > is for openjdk-8 to be reintroduced for Bullseye, but the question is
> > who gets to maintain it?
> 
> Why did they stop providing the bundled JDK?  Do the AdoptOpenJDK
> builds work?  If not, then why would a Debian build of openjdk-8 be
> any different?

JDK 8 is already EOL, current JDK LTS release is 11. I would advice against 
putting an EOLed product into a not yet released Bullseye

Java has pretty good backwards compatibility so code that works on JDK 8 should work on 
JDK 11

Just my 2 cents.

-- 
Ihor Antonov
https://useplaintext.email

[toc] | [prev] | [next] | [standalone]


#5803

FromGraham Inggs <ginggs@debian.org>
Date2020-04-09 22:30 +0200
Message-ID<zTLYd-6tb-1@gated-at.bofh.it>
In reply to#5801
On Thu, 9 Apr 2020 at 21:11, Florian Weimer <fw@deneb.enyo.de> wrote:
> Why did they stop providing the bundled JDK?

>From their release notes [1]:

Oracle JDK 8 JRE, required by Nsight Eclipse Edition and Visual
Profiler, are no longer included in the CUDA Toolkit as of version
10.1 Update 2, due to Oracle upgrade licensing changes.

> Do the AdoptOpenJDK
> builds work?  If not, then why would a Debian build of openjdk-8 be
> any different?

I don't know about the AdoptOpenJDK builds, but Visual Profiler and
Nsight do work with openjdk-8 8u252-b07-1 from unstable.


[1] https://docs.nvidia.com/cuda/archive/10.1/cuda-toolkit-release-notes/index.html

[toc] | [prev] | [next] | [standalone]


#5804

FromAndreas Beckmann <anbe@debian.org>
Date2020-04-09 23:00 +0200
Message-ID<zTMrg-6D6-3@gated-at.bofh.it>
In reply to#5803
On 09/04/2020 22.12, Graham Inggs wrote:
> I don't know about the AdoptOpenJDK builds, but Visual Profiler and
> Nsight do work with openjdk-8 8u252-b07-1 from unstable.
> 
> [1] https://docs.nvidia.com/cuda/archive/10.1/cuda-toolkit-release-notes/index.html

The version previously bundled by nvidia with nvidia-cuda-toolkit (up to
10.1.168) is an ancient 8u77 amd64 build, packaged as
nvidia-openjdk-8-jre in non-free.

For the purposes of src:nvidia-cuda-toolkit, a stripped down version of
openjdk-8 should be sufficient: only amd64 and ppc64el builds, only -jre
(no -jdk), and it could be moved to contrib to reduce exposure even further.



Andreas

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.security


csiph-web