jtreg fails to locate its own lib directory
Bug #1887587 reported by
Tiago Stürmer Daitx
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| jtreg (Debian) |
Fix Released
|
Unknown
|
|||
| jtreg (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
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/
if [ -z "${JTREG_HOME}" ]; then
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.
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in jtreg (Ubuntu): | |
| status: | New → Fix Released |
| Changed in jtreg (Debian): | |
| status: | Unknown → Fix Released |
To post a comment you must log in.
This bug was fixed in the package jtreg - 5.1-b01-1ubuntu1
---------------
jtreg (5.1-b01-1ubuntu1) groovy; urgency=medium
* d/p/launcher.patch: set JTREG_HOME earlier. (Closes: #965047,
LP: #1887587).
-- Tiago Stürmer Daitx <email address hidden> Tue, 14 Jul 2020 23:47:56 +0000