Your message dated Mon, 27 Aug 2018 13:34:06 +0000
with message-id <[email protected]>
and subject line Bug#906785: fixed in ant 1.10.5-2
has caused the Debian Bug report #906785,
regarding version warping patch is overly aggressive
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 [email protected]
immediately.)


-- 
906785: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906785
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ant
Version: 1.10.5-1
Severity: important

The Debian ant package is built with a patch "0013-auto-adjust-target.patch"
that forces the Java target version number to 7.  The utterly breaks the
ability to use Debian ant for building Java applications that get wrapped up
in installer packages targeting other operating systems, including non-Debian 
Linux, Windows, and Mac OS X.  Specifically, many Mac OS X users apparently
are still being given Java 1.6 as the most recent version certified on their
operating system, and while in theory it's possible for them to move to 
Java 1.8 through a download from Oracle, this apparently takes most Apple
customers way outside their comfort zone.

If the javac delivered by our default-jdk actually had such a version 
restriction, we'd tell our customers to just cope with it.  But it turns out
that even openjdk-11-jdk's javac will take -source and -target assertions
of 1.6 and correctly emit compiled classes that assert major version 50, 
which is compatible with Java 1.6.  Any package built with ant, however, is
forced to version 7 which results in compiled classes that assert major
version 51, which will not run on Java 1.6!

Please fix ant to not impose a version warp that's more restrictive than
actually required by default-jdk, so that we can continue to use Debian as
a build platform supporting customers who are "stuck" on Java 1.6.

Frankly, I'm not sure having this patch in the Debian package at all is a 
good idea.  Isn't it better to let javac itself emit an error message if/when
a version actually becomes supported, and let the developer learn about
versions and how to update their ancient assertions when needed rather than
hide this problem?

Regards,

Bdale

--- End Message ---
--- Begin Message ---
Source: ant
Source-Version: 1.10.5-2

We believe that the bug you reported is fixed in the latest version of
ant, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Markus Koschany <[email protected]> (supplier of updated ant package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Mon, 27 Aug 2018 14:57:47 +0200
Source: ant
Binary: ant ant-optional ant-doc
Architecture: source
Version: 1.10.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 
<[email protected]>
Changed-By: Markus Koschany <[email protected]>
Description:
 ant        - Java based build tool like make
 ant-doc    - Java based build tool like make - API documentation and manual
 ant-optional - Java based build tool like make - optional libraries
Closes: 906785
Changes:
 ant (1.10.5-2) unstable; urgency=medium
 .
   * Team upload.
   * Lower the minimum required source/target level to 1.6 again.
     This is acceptable for OpenJDK 11 but must be reverted for OpenJDK 12.
     Thanks to Bdale Garbee for the report and patch. (Closes: #906785)
   * Declare compliance with Debian Policy 4.2.1.
Checksums-Sha1:
 f132951842af23b694141f4ad7ca910ccb50671b 2537 ant_1.10.5-2.dsc
 4c23896b0e8aeb67d941494da47ba9cd0c8e7f32 19100 ant_1.10.5-2.debian.tar.xz
 1d4abbdba2c55edb49f5d44ec242412d2835ead7 11999 ant_1.10.5-2_amd64.buildinfo
Checksums-Sha256:
 f5b9bcedc6b22e72a9ff901d28664a277dec31ab1a15ccd6527775519613d8b9 2537 
ant_1.10.5-2.dsc
 9c5e0df8cef5fa884805540ee57046f89d0bd108bdd9f78e455322a8a0b27c91 19100 
ant_1.10.5-2.debian.tar.xz
 2b1a98d787778d4783535eb7edf189536991707ca887767b7a0a998eda2f1cda 11999 
ant_1.10.5-2_amd64.buildinfo
Files:
 0d804577dab4209173824e6c427eb465 2537 java optional ant_1.10.5-2.dsc
 df9d7f12f4c02a1f4002eefd49581a21 19100 java optional ant_1.10.5-2.debian.tar.xz
 6f407c2a4652de48b20da82c42029bbb 11999 java optional 
ant_1.10.5-2_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAluD921fFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD
RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp
YW4ub3JnAAoJENmtFLlRO1HkphgP/2atWeLVKPEzjoSEhlurJfdLBIeQ0042KfXq
e5SV9NMRaHJ4YVJXh1o98pYUUIhAjLanfxr9npw4hZMUyaJdXAKjZThNeu7Sn1SA
IoBT3TYzaYlM82bm8L3H0hCp0SAZFQ3rxx8sRi9kIdp0ADCBBvdZu9ijzHni3Hpi
yb0Lx9K+kd3I3Crtd+pncgSQyQx5yEmsAjVdO88LUuRjYVF/bw/Df2EKAjQDdnPO
588OLzPuoG1sCqfgtj8Gg/zOvV8dtfNax4/kd4zfss/wXmrQM6AhbMSGygZz+nmQ
6N8u8HUJBPBO8T7p3nIZPZg08FpDzOx89YGfWO6FU2JseMVxmm3pJ7ZZLFH3TDXD
ZmwnVhtjo2NxL760Y7k95uykMtn74mA04hmduqclZAKv66Zy7TfEoXC+/LJI0K2S
RHPSDN5/L+URJBaVMDfRG8KRT0LwqZeXevVKlKRKLGrl61hIJfWPWkLQD8TZsImx
9ZuNuKTqynCFH+sev+Oth8Lov9hhubvn4npgaoA+nMxRAbhvO4EA63QZswmBN6oI
ngLMaj4EnY96+dgw/j87YENSVEQuUKmcZXs81qzSv3pU8wTOtvy2qbRg7j0xbOlU
09KyGB5+d41MrZfkiQOzg7orGumfNQijldFsDcPGLwqCJzG2Q0J11uGsmrmqwbkE
3clR/MGv
=4oCs
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to