find Java utilities seem to fail on Debian (sid)

[lopippo]

Greetings, dear DAPS developers,

I am currently stumbling over a glitch that prevents daps to build a document. I am not sure what is the culprit of this glitch.

In a pristine debian unstable chroot, I install daps. Fine. Then, I make my user manual and I get this error message:

Fatal error: The document contains XML errors:
[warning] /usr/share/daps/libexec/daps-jing: No java runtime was found

I thus try to execute each daps-jing line separately:

# . /usr/lib/java-wrappers/java-wrappers.sh (ok)
# find_java_runtime openjdk || find_java_runtime
[warning] -bash: No java runtime was found

So I try the commands separately:

# find_java_runtime openjdk

out of curiosity:

# find_java_runtime

What I understand is that the validate.mk:67 line stores the output of the command to check if there was an error or not:

$(eval FAULTY_XML=$(shell unset VERBOSE && $(JING_WRAPPER) $(JING_FLAGS) $(DOCBOOK5_RNG) $(PROFILED_MAIN) 2>&1))

Indeed, if I add the following:
echo "FR $(FAULTY_XML)" right after the line 67,
FAULTY_XML contains this:
FR [warning] /usr/share/daps/libexec/daps-jing: No java runtime was found

Oddly enough, if I now remove the 'shell unset VERBOSE &&' part of the statement, then I have no more the error:
I get only "FR" for the output.

Then, the documentation builds just fine, which indicates that the "find_java*" utilities have failed.

I do not know where this problem originated (nor when) but I wanted to ask you if you had an idea over how to fix this.

Most sincerely,
Filippo

[fsundermeyer]

Hi Filipo,

hmm, the jing wrapper script for Debian differs significantly from the one we are using for openSUSE. It is pretty old (2015) and may not work anymore.
Would you mind trying libexec/daps-jing.generic instead?

Best regards, Frank

[lopippo]

Greetings, Frank

What I do not understand is how the simple removal of 'shell unset VERBOSE &&' from validate.mk line 67 makes the problem go away.

Sincerely
Filippo