Your message dated Wed, 15 Jul 2020 04:48:37 +0000
with message-id <[email protected]>
and subject line Bug#965047: fixed in jtreg 5.1-b01-2
has caused the Debian Bug report #965047,
regarding jtreg won't run as it can't locate its own jar file
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
965047: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965047
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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

--- End Message ---
--- Begin Message ---
Source: jtreg
Source-Version: 5.1-b01-2
Done: tony mancill <[email protected]>

We believe that the bug you reported is fixed in the latest version of
jtreg, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
tony mancill <[email protected]> (supplier of updated jtreg package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Tue, 14 Jul 2020 21:28:47 -0700
Source: jtreg
Architecture: source
Version: 5.1-b01-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 
<[email protected]>
Changed-By: tony mancill <[email protected]>
Closes: 965047
Changes:
 jtreg (5.1-b01-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Tiago Stürmer Daitx ]
   * d/p/launcher.patch: set JTREG_HOME earlier. (Closes: #965047,
     LP: #1887587).
 .
   [ tony mancill ]
   * Use debhelper-compat 13
   * Use https URL for Homepage in debian/control
   * Freshen years in debian/copyright and update Source: link
   * Set "Rules-Requires-Root: no" in debian/control
Checksums-Sha1:
 6ed083c5d46031bf8790c54c370ce72f40bb0368 2044 jtreg_5.1-b01-2.dsc
 ddc82ae96eb9a774104cb1ad116dc56989939036 6216 jtreg_5.1-b01-2.debian.tar.xz
 b050c62580c99d70f8d3f629d67a2840bd782748 10999 jtreg_5.1-b01-2_amd64.buildinfo
Checksums-Sha256:
 264ac32546f232016b4e576d72c2571865c541b2c0a1b02a1e9948d166d677f2 2044 
jtreg_5.1-b01-2.dsc
 d014af00acc56f21eb5ea34645e6e9aa2abd939141a6020405d64879ceaf0f6c 6216 
jtreg_5.1-b01-2.debian.tar.xz
 8a17f3c60fdb0bb027763893726603d430595e1dae9fda061c1ed468ac16b88c 10999 
jtreg_5.1-b01-2_amd64.buildinfo
Files:
 1e3e06b8e67ed25d2969f70cca27c5bb 2044 java optional jtreg_5.1-b01-2.dsc
 b0cb3156851f25beccd7c5799d1ac5cc 6216 java optional 
jtreg_5.1-b01-2.debian.tar.xz
 06bfc48402b534924949bc01bb196d56 10999 java optional 
jtreg_5.1-b01-2_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQJIBAEBCgAyFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAl8Oh3cUHHRtYW5jaWxs
QGRlYmlhbi5vcmcACgkQIdIFiZdLPpad8RAAjaFMrwbUFCUrdakW1ZSvKXtMS00J
XPTjOJu882SUAJErew0/ksJhWi8jmrpgMJY2FzFx8LTszwMflgwIDXOCXXzR+ggs
MHypIwQG0E+np0j/qho6li5wQJE+SeTXl9rCsYX6VOlEyzMZLPDLhiUjDE6GELt9
aLjR3ZPQHa7WHwNiEE+/QJh1qyrYV4dT3SPlj6uDZvfqfJNddA7bZmnW/nf4a2pI
UGsLC7hnT02gtmbaduafKmXRPLEnsLpWRbm2HfnKy5eDrOPM2+L9yBQOzxbbe1GV
fiNTBVG4kOZiyCsj+g8F92dmPpBPEnAespFWyIef+mUKHfrQPkG2dT89/cvRX75s
+peBeXBkJszsCNHSftq7dbOG95zPX6FtPX/qMbRSMxe1/yfVF50UbdhIkY+c2fPg
qcco6B+6CupYBOnWr6xcya+7ZMNi94C6Gf4MVXzSppgey6GIBnAkomWDAjFSdBJW
XZXC8gcvP8GZV0PovrnUGUzOq3OKx8UolAIdAMqvJwItqAtTOPx1iMSMqGRkzFgX
YMrTS3NrUc4BN7P92QmrbvvP+ynWKTiKKPLW7GFG5YBftZMYEzQV5TI/D6ZK02ab
o42R0kCGOdU2Py6l75lsFj6FZ5250NJLDSR4R16tv8cy/DY1NioqBKUUZtCaGTbE
wAegOyCum5aIcEM=
=rKT8
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to