Hi Moritz, Moritz Muehlenhoff, on 2025-04-21: > The regular copy in the archive is libitext5-java, could beast-mcmc > be fixed to use that one instead, so that we can remove libitext1-java?
I have examined the situation in beast-mcmc and noticed that the build process already pulled libitext5-java. I have also run the commented out junit test suite. While the suite does report failure and error messages, the overall process reports having successfully executed, so not sure what to trust. Checking with and without the build dependency libitext1-java, I also noticed no regressions in unit tests. I consider the option of just removing libitext1-java from the build dependencies, to avoid creating a future adherence to libitext5-java if not strictly needed. My current assumption is that the newer libitext5-java has been already in use more or less by accident, and that removing libitext1-java will bring no further changes. Actually checking with diffoscope shown no difference that was obviously related to libitext1-java removal apart from metainformation here and there, but I must admit the diff was cluttered with timestamp differences, thus slightly hard to read, and I may have missed things. Also, attempting to run a few workloads against example files provided by beast-mcmc-examples shows no visible changes with the current package in unstable or without libitext1-java. Would that help to have such change brought to trixie? Have a nice day, :) -- .''`. Étienne Mollier <emoll...@debian.org> : :' : pgp: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da `. `' sent from /dev/pts/2, please excuse my verbosity `- on air: Anubis Gate - Entangled (Genesis Cover)
signature.asc
Description: PGP signature
