Bug#965047: jtreg won't run as it can't locate its own jar file

[Tiago Stürmer Daitx]

Package: jtreg
Version: 5.1-b01-1
Severity: important

Dear Maintainer,

Since jtreg 5.1-b01-1 it will no longer run without having JTREG_HOME (or
JT_HOME) explicitly set on the environment, previous versions worked ok.

It will exit 1 when trying to run it:
$ jtreg
Cannot determine JTREG_HOME; please set it explicitly

The reason is a change in debian/patches/launcher.patch that adds the check

 if [ -z "${JTREG_HOME}" ]; then
     JTREG_HOME="/usr/share/jtreg"
 fi

too further down compared to the previous jtreg version. This causes the code
to search for lib/jtreg.jar in the script's path (/usr/bin) first, which does
not work and then calls exit 1.

That check is added exclusively for Debian/Ubuntu by d/p/launcher.patch and
should come before jtreg will try to look for lib/jtreg.jar by itself.

This also affects openjdk autopkgtests, which don't get run becuse jtreg
fails to start.

Thanks!

-- System Information:
Debian Release: bullseye/sid
  APT prefers focal
  APT policy: (500, 'focal'), (400, 'focal-proposed')
Architecture: amd64 (x86_64)

Kernel: Linux 5.4.0-26-generic (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled