Bug#1041282: jtreg6 - okay to upload upstream version 6.2+1?

[tony mancill]

On Wed, Aug 16, 2023 at 09:28:39AM +1200, Vladimir Petko wrote:
> Hi,
> 
>  The build.xml is not supported by the upstream, so I have updated the
> patch to include rule changes to use the provided Makefile[1].
> 
> Changes:
>   * Use Makefile to build jtreg (LP: #2031041).
>     - Use --release option in Makefile compile options.
>     - d/p/*: drop build.xml patches.
>     - d/control: add libguice-java, zip.

Hello Vladimir, hi Emmanuel:

Vladimir, thank you for this patch (and others).  I applied it to the
current source repo and rebuild all of the build r-deps before I
realized that the source repo contains 6.2+1 [1] (not 6.1+2), which
hasn't been uploaded.

Are there any considerations or concerns about going ahead with an
upload of 6.2+1?  As I said, I was able to build openjdk-11, -17, and
-19 with that version.

Thanks,
tony

[1] https://salsa.debian.org/java-team/jtreg/-/commit/18fe40fc470b04bc735b425bba250db61340fcb3
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-java-maintainers/attachments/20230818/b15e73a2/attachment-0001.sig>