Hello everyone,
we are aiming to remove libdb-java package from Fedora-rawhide, as we are currently preparing for jdk update from jdk-1.8 to jdk-11 in Fedora rawhide. The problem is that we are unable to rebuild this package with jdk-11. It is still possible to "hack" it and rebuild it with jdk-1.8, but that can cause unexpected runtime behaviour according to JVM-11, which will soon be default in Fedora-rawhide.
There seems to be no packages, which depend directly to libdb-java and upstream does not support version 5.3.28 anymore.
If anyone has any reasons why this should not be made, or someone is currently active user of this JDBC connector, please leave a comment with your opinion in the tracker [1] mentioned below.
There is also an existing tracker for deprecating libdb in Fedora [2], so this can be understand as a first step.
Additional info about jdk-11 here [3].
Best regards,
Ondrej Dubaj Associate Software Engineer Red Hat
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1846398 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1834842 [3] https://fedoraproject.org/wiki/Changes/Java11#Intermediate_step_build_with_j...
* Ondrej Dubaj:
we are aiming to remove libdb-java package from Fedora-rawhide, as we are currently preparing for jdk update from jdk-1.8 to jdk-11 in Fedora rawhide. The problem is that we are unable to rebuild this package with jdk-11. It is still possible to "hack" it and rebuild it with jdk-1.8, but that can cause unexpected runtime behaviour according to JVM-11, which will soon be default in Fedora-rawhide.
Out of curiosity, what is the exact problem?
Thanks, Florian
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 ?
Thanks, Ondrej
On Thu, Jun 11, 2020 at 10:28 PM Florian Weimer fweimer@redhat.com wrote:
- Ondrej Dubaj:
we are aiming to remove libdb-java package from Fedora-rawhide, as we are currently preparing for jdk update from jdk-1.8 to jdk-11 in Fedora rawhide. The problem is that we are unable to rebuild this package with jdk-11. It is still possible to "hack" it and rebuild it with jdk-1.8, but that can cause unexpected runtime behaviour according to JVM-11, which will soon be default in Fedora-rawhide.
Out of curiosity, what is the exact problem?
Thanks, Florian
* 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
On 6/15/20 9:13 AM, Florian Weimer 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).
Maybe. However upstream of is dead. And usptream confirmed that they are unable to verify that it works in JDK11.
Imho droppoing such possibly instbale package is probably good way. If it will be missed, then it can be returned, and the one wishing its return will be used as tester.
Is there some replacemnt for this subpackage? At least theoretical?
Thanks, Florian _______________________________________________ java-devel mailing list -- java-devel@lists.fedoraproject.org To unsubscribe send an email to java-devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/java-devel@lists.fedoraproject...
Agree,
I am not aware of any replacement of this JDBC connector. As you said, it can be easily returned if it would be missed.
On Mon, Jun 15, 2020 at 9:27 AM Jiri Vanek jvanek@redhat.com wrote:
On 6/15/20 9:13 AM, Florian Weimer 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).
Maybe. However upstream of is dead. And usptream confirmed that they are unable to verify that it works in JDK11.
Imho droppoing such possibly instbale package is probably good way. If it will be missed, then it can be returned, and the one wishing its return will be used as tester.
Is there some replacemnt for this subpackage? At least theoretical?
Thanks, Florian _______________________________________________ java-devel mailing list -- java-devel@lists.fedoraproject.org To unsubscribe send an email to java-devel-leave@lists.fedoraproject.org Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives:
https://lists.fedoraproject.org/archives/list/java-devel@lists.fedoraproject...
-- Jiri Vanek Senior QE engineer, OpenJDK QE lead, Mgr. Red Hat Czech jvanek@redhat.com M: +420775390109
* Jiri Vanek:
Is there some replacemnt for this subpackage? At least theoretical?
For the JDBC connector to SQLite, there's sqlite-jdbc and javasqlite. But the on-disk format will be different.
For the key-value store, there is the je package, but again the on-disk format is different.
Thanks, Florian
I don;t think this is a reason not removing libdb-java subpackage from Fedora-Rawhide. If you are an active user of it, or you know somebody who actively uses it, we can discuss more about these issues.
Thanks, Ondrej
On Mon, Jun 15, 2020 at 9:54 AM Florian Weimer fweimer@redhat.com wrote:
- Jiri Vanek:
Is there some replacemnt for this subpackage? At least theoretical?
For the JDBC connector to SQLite, there's sqlite-jdbc and javasqlite. But the on-disk format will be different.
For the key-value store, there is the je package, but again the on-disk format is different.
Thanks, Florian
Hello everyone,
today I am removing libdb-java subpackage from Fedora-rawhide (see messages above for more info). If someone of you will face any problems, please let us know.
Thanks! Regards,
Ondrej
On Wed, Jun 24, 2020 at 11:27 AM Ondrej Dubaj odubaj@redhat.com wrote:
I don;t think this is a reason not removing libdb-java subpackage from Fedora-Rawhide. If you are an active user of it, or you know somebody who actively uses it, we can discuss more about these issues.
Thanks, Ondrej
On Mon, Jun 15, 2020 at 9:54 AM Florian Weimer fweimer@redhat.com wrote:
- Jiri Vanek:
Is there some replacemnt for this subpackage? At least theoretical?
For the JDBC connector to SQLite, there's sqlite-jdbc and javasqlite. But the on-disk format will be different.
For the key-value store, there is the je package, but again the on-disk format is different.
Thanks, Florian
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
java-devel@lists.fedoraproject.org
-
Florian Weimer -
Jiri Vanek -
Ondrej Dubaj