You are of course correct, I've replaced the java-runtime dep with -headless.
We can't really do
much about the deprecation message, upstream wants you to use their bundled jdk
(and nodejs) to
ease their support system. However this sounds like a security nightmare to me,
if I fix a CVE of
the s
Thanks a lot for your work! I already managed to migrate to OpenSearch
without major issues.
I am a little confused about the java dependency. It requires
java-runtime instead of java-runtime-headless as Elasticsearch did.
However on launch I get the following warning: "no-jdk distributions
that d
Hello everyone,
As mentioned in a previous mail [0] I've taken some time to bring the
ElasticSearch fork OpenSearch
to Community [1].
I've also added twelve plugin packages, a package for the Kibana fork
OpenSearch Dashboards and
eight plugin packages for that. Additionally I packaged the opens
