I edited the autoconf check and it seems there are other issues, which are causing problems. I also contacted upstream and they do not have any experience with this version working with jdk-11 or jvm-11. I see it as a high risk to "somehow" rebuild it

and push it to rawhide. In addition, there is a deprecation announcement to whole libdb, so I consider this as a good first step.

Thanks,

Ondrej

On Mon, Jun 15, 2020 at 9:13 AM Florian Weimer <fweimer@redhat.com> wrote:

* Ondrej Dubaj:

> The problem is unknown runtime behaviour of libdb-java (build with
> jdk-1.8, as it is unable to build with jdk-11) with JVM-11. Are you an
> active user of libdb java ?

I am not.

Upon second thought, it doesn't seem to make sense to preserve
libdb-java (although I expect that it's only necessary to fix the
autoconf check).

Thanks,
Florian