Hi. I am not an expert on Debian policy, so the following may be incorrect, but this was my reasoning for re-opening the bug:
On Wed, Sep 21, 2022 at 2:21 AM Sebastian Ramacher <sramac...@debian.org> wrote: > Please don't reopen it. We have version tracking to track this kind of > thinks. For the bullseye version, the bug was still open. Reclosing. As far as I can see, this issue is fixed in bookworm because 1:1.3.2-1 has an upstream fix, there is no fix at all to this issue in stable 1:1.2.1-4+deb11u1. Aren't FTBFS, and other critical software bugs that prevent runtime use of the library entirely, considered a serious Debian policy violation that should be fixed with an upload to stable-proposed-updates? Specifically, I am suggesting a new package 1:1.2.1-4+deb11u2 for inclusion in the next bullseye point release. This keeps the existing upstream version and packaging used for bullseye, with just one additional patch that fixes the FTBFS and runtime issue. >From experimentation the FTBFS and the runtime crash occur with Java 11 (i.e. stable's default-jdk) and Java 17. But not under Java 8. So it may be difficult to observe the FTFBS if one builds the package in a non-isolated environment using Java 8. Thanks, Christian
