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

Groups > linux.debian.maint.java > #12599

Re: OpenJDK package - JTREG 7.1

Show all headers | View raw

Hi,

 Unfortunately jtreg6 is required. 6.1 is used by OpenJDK 17 and 6.1.1
is used by OpenJDK 18 and 19.  Java 17 is going to be supported until
2030[1] and Java 21 is going to be supported until 2028 [2], so both
packages are warranted.

Best Regards,
 Vladimir.
[1]  https://javaalmanac.io/jdk/17/
[2] https://javaalmanac.io/jdk/21/

On Thu, Mar 2, 2023 at 1:31 PM Thorsten Glaser <t.glaser@tarent.de> wrote:
>
> On Thu, 2 Mar 2023, Vladimir Petko wrote:
>
> >OpenJDK 20.  We still need jtreg6 and jtreg packages for older
> >versions of OpenJDK.
>
> openjdk-8 was switched to jtreg6 recently. See if doko will
> follow for 11.
>
> >I was wondering if it would be acceptable for me
> >to file an intent to package proposal for JTREG7 and package it?
>
> Sure, why not (unless someone else is already working on it).
>
> Is a new package needed anyway? Can’t this just be an upgrade
> to jtreg6 (sure that will then look weird as jtreg6 version 7.1-1
> but we have lots of such situations)? Is it incompatible somehow?
>
> bye,
> //mirabilos
> --
> Infrastrukturexperte • tarent solutions GmbH
> Am Dickobskreuz 10, D-53121 Bonn • http://www.tarent.de/
> Telephon +49 228 54881-393 • Fax: +49 228 54881-235
> HRB AG Bonn 5168 • USt-ID (VAT): DE122264941
> Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg
>
>                         ****************************************************
> /⁀\ The UTF-8 Ribbon
> ╲ ╱ Campaign against      Mit dem tarent-Newsletter nichts mehr verpassen:
>  ╳  HTML eMail! Also,     https://www.tarent.de/newsletter
> ╱ ╲ header encryption!
>                         ****************************************************

Back to linux.debian.maint.java | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

OpenJDK package - JTREG 7.1 Vladimir Petko <vladimir.petko@canonical.com> - 2023-03-02 00:50 +0100
  Re: OpenJDK package - JTREG 7.1 Thorsten Glaser <t.glaser@tarent.de> - 2023-03-02 01:40 +0100
    Re: OpenJDK package - JTREG 7.1 Vladimir Petko <vladimir.petko@canonical.com> - 2023-03-02 02:00 +0100
      Re: OpenJDK package - JTREG 7.1 Thorsten Glaser <t.glaser@tarent.de> - 2023-03-02 02:10 +0100
        Re: OpenJDK package - JTREG 7.1 Vladimir Petko <vladimir.petko@canonical.com> - 2023-03-03 02:30 +0100
          Re: OpenJDK package - JTREG 7.1 Thorsten Glaser <t.glaser@tarent.de> - 2023-03-03 04:00 +0100
            Re: OpenJDK package - JTREG 7.1 Vladimir Petko <vladimir.petko@canonical.com> - 2023-03-14 03:50 +0100
              Re: OpenJDK package - JTREG 7.1 Thorsten Glaser <t.glaser@tarent.de> - 2023-03-14 10:40 +0100
                Re: OpenJDK package - JTREG 7.1 Vladimir Petko <vladimir.petko@canonical.com> - 2023-03-14 20:00 +0100
                Re: OpenJDK package - JTREG 7.1 Thorsten Glaser <t.glaser@tarent.de> - 2023-03-14 21:00 +0100
                Re: OpenJDK package - JTREG 7.1 Vladimir Petko <vladimir.petko@canonical.com> - 2023-03-15 08:30 +0100
                Re: OpenJDK package - JTREG 7.1 Emmanuel Bourg <ebourg@apache.org> - 2023-03-15 10:50 +0100
                Re: OpenJDK package - JTREG 7.1 Vladimir Petko <vladimir.petko@canonical.com> - 2023-03-15 20:20 +0100
    Re: OpenJDK package - JTREG 7.1 Emmanuel Bourg <ebourg@apache.org> - 2023-03-15 16:30 +0100
      Re: OpenJDK package - JTREG 7.1 Vladimir Petko <vladimir.petko@canonical.com> - 2023-03-15 23:10 +0100
        Re: OpenJDK package - JTREG 7.1 Vladimir Petko <vladimir.petko@canonical.com> - 2023-03-15 23:20 +0100
          Re: OpenJDK package - JTREG 7.1 Vladimir Petko <vladimir.petko@canonical.com> - 2023-03-28 22:40 +0200
            jtreg 7 vs. jtreg6 vs. testng vs. openjdk-8 (was Re: OpenJDK package  - JTREG 7.1) Thorsten Glaser <t.glaser@tarent.de> - 2023-03-29 21:30 +0200
        Re: OpenJDK package - JTREG 7.1 Thorsten Glaser <t.glaser@tarent.de> - 2023-03-15 23:20 +0100

csiph-web