elasticsearch-8.17 introduced dependency on jdk. Without a jdk installed, it fails to start complaining about jdk.attach module not found. After installing virtual/jdk:17, it works without a problem Reproducible: Always
Created attachment 920379 [details, diff] Depend on jdk insted of on jre
(In reply to nebojsa from comment #0) > elasticsearch-8.17 introduced dependency on jdk. Without a jdk installed, it > fails to start complaining about jdk.attach module not found. > After installing virtual/jdk:17, it works without a problem > > Reproducible: Always Usually if using virtual/jdk, it should go in DEPEND according to https://wiki.gentoo.org/wiki/Java_Developer_Guide#JDK.2FJRE. In RDEPEND you put virtual/jre - and don't forget to inherit either of java-pkg-2.eclass of java-pkg-opt-2.eclass.
(In reply to Volkmar W. Pogatzki from comment #2) > (In reply to nebojsa from comment #0) > > elasticsearch-8.17 introduced dependency on jdk. Without a jdk installed, it > > fails to start complaining about jdk.attach module not found. > > After installing virtual/jdk:17, it works without a problem > > > > Reproducible: Always > > Usually if using virtual/jdk, it should go in DEPEND according to > https://wiki.gentoo.org/wiki/Java_Developer_Guide#JDK.2FJRE. > In RDEPEND you put virtual/jre - and don't forget to inherit either of > java-pkg-2.eclass of java-pkg-opt-2.eclass. This package is not compiled - it is a binary bundle, that's why it does not inherit java-pkg-*.eclass. Further, it depends on jdk runtime, and not on jre runtime. Running it with jre runtime is what produces the error. If anything, package name could be changed to better reflect its contents, to elasticsearch-bin, and a warning could be issued to the user about either setting up jdk as system-vm or setting ES_JAVA_HOME in /etc/conf.d/elasticsearch to point to one.
afaik, binary blob should never depend on jdk. if it does, there's something wrong.