[xml/sgml-pkgs] Bug#834554: jing-trang: spurious warning "No java runtime was found"

[Vincent Lefevre]

Source: jing-trang
Version: 20131210+dfsg+1-5
Severity: normal

Since a recent upgrade, when I run jing or trang, I now get:

[warning] /usr/bin/jing: No java runtime was found

or

[warning] /usr/bin/trang: No java runtime was found

then everything is OK.

The problem comes from the jing/trang sh wrapper, which does:

find_java_runtime openjdk sun || find_java_runtime

It is "find_java_runtime openjdk sun" that outputs this warning.
But such a warning is annoying if the java runtime is obtained
by the second find_java_runtime. So, it should be silenced.

A way to silence the warnings is to do:

java_warning() { :; }

before these calls, though this is a bit of a hack.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.6.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)