[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1024039: marked as done (Current default JDK should be updated in Lintian)

Your message dated Sun, 29 Jan 2023 00:38:51 +0100
with message-id <20230128233851.6wao5tqp645osh2w@sym.noone.org>
and subject line Re: Bug#1024039: Current default JDK should be updated in Lintian
has caused the Debian Bug report #1024039,
regarding Current default JDK should be updated in Lintian
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1024039: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024039
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: lintian
Version: 2.115.3
Severity: normal

Dear Maintainer,

Recently, java-common was updated in unstable and then in testing, it changes
the default JDK in Debian from OpenJDK11 to OpenJDK17. Thus I think the line 21
in data/java/constants should be changed from
    default-bytecode-version = 56
to
    default-bytecode-version = 61
in order to avoid warnings like

--------------------------8<--------------------------
W: beast2-mcmc: incompatible-java-bytecode-format Java17 version (Class format: 61)
N: 
N:   The package contains Java class files with a minimum requirement on the
N:   listed Java version. This Java version is not supported by the default JVM
N:   in Debian and is therefore likely to be a mistake.
N: 
N:   Please refer to Bug#673276 for details.
N: 
N:   Visibility: warning
N:   Show-Always: no
N:   Check: languages/java
N: 
--------------------------8<--------------------------

which I got with beast2-mcmc 2.7.1+dfsg-1. The package was successfully built
using OpenJDK17 and is now in unstable.
I also just got a similar warning with libjgraph-java, which should hit
unstable within a couple of hours.

Thanks for all the work on Lintian!

Cheers,

-- 
Pierre

--- End Message ---
--- Begin Message --- 
Version: 2.116.1

Hi Pierre!

Pierre Gruet wrote:
> Recently, java-common was updated in unstable and then in testing, it changes
> the default JDK in Debian from OpenJDK11 to OpenJDK17. Thus I think the line 21
> in data/java/constants should be changed from
>     default-bytecode-version = 56
> to
>     default-bytecode-version = 61
> in order to avoid warnings like
> 
> --------------------------8<--------------------------
> W: beast2-mcmc: incompatible-java-bytecode-format Java17 version (Class format: 61)

Interestingly this did not show up in the test suite before I uploaded
2.116.0 on 17th of January 2023. It though did show up while testing
for the 2.116.1 upload. Hence I fixed with the last commit for 2.116.1
(https://salsa.debian.org/lintian/lintian/-/commit/76b92553) which I
uploaded on 25th of January including that fix.

Hence closing. Thanks for the bug report anyway and sorry for not
having noticed it in time!

Will update the changelog entry for 2.116.1 retroactively to mention
this bug report.

		Regards, Axel
-- 
 ,''`.  |  Axel Beckert <abe@debian.org>, https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-    |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

--- End Message ---
Reply to: