Your message dated Wed, 03 Sep 2025 20:44:47 +0000
with message-id <[email protected]>
and subject line Bug#1017761: fixed in python-jpype 1.6.0-1
has caused the Debian Bug report #1017761,
regarding java.lang.ClassNotFoundException: 
org.jpype.classloader.DynamicClassLoader
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.)


-- 
1017761: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017761
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: python3-jpype
Version: 1.4.0-2
Severity: normal

Due to how the org.jpype.jar is packaged 
(https://salsa.debian.org/python-team/packages/python-jpype/-/commit/44a8befe0b856609a4095f5d9e3979752e367ad8),
 
jpype.startJVM() doesn't work out of the box as documented in upstream 
documentation:

    $ python3 -c 'import jpype; jpype.startJVM()'
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/usr/lib/python3/dist-packages/jpype/_core.py", line 218, in 
startJVM
        _jpype.startup(jvmpath, tuple(args),
    SystemError: java.lang.ClassNotFoundException: 
org.jpype.classloader.DynamicClassLoader

This is because it's expected to be in 
/usr/lib/python3/dist-packages/org.jpype.jar 
(https://github.com/jpype-project/jpype/blob/24a2b95aefc2a59e7cf2c362a92ee5c6b13eb94f/native/common/jp_classloader.cpp#L74)
 
and Debian unfortunately only moves the jar, but doesn't patch jpype to 
look for it in the new location.

As a workaround, one can explicitly add the jar to classpath:

    $ python3 -c 'import jpype; 
jpype.startJVM(classpath=["/usr/share/java/org.jpype.jar"])'

Unfortunately, this isn't documented anywhere.

-- System Information:
Debian Release: bookworm/sid
  APT prefers stable-security
  APT policy: (990, 'stable-security'), (990, 'testing'), (500, 
'unstable-debug'), (500, 'testing-debug'), (500, 'stable-debug'), (500, 
'unstable'), (500, 'stable'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.18.0-3-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CPU_OUT_OF_SPEC, TAINT_USER, TAINT_WARN
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-jpype depends on:
ii  default-jre                                       2:1.11-72
ii  default-jre-headless [java6-runtime-headless]     2:1.11-72
ii  libc6                                             2.34-3
ii  libgcc-s1                                         12.1.0-8
ii  libstdc++6                                        12.1.0-8
ii  openjdk-11-jre-headless [java6-runtime-headless]  11.0.16+8-1
ii  python3                                           3.10.5-3
ii  python3-numpy [python3-numpy-abi9]                1:1.21.5-1+b1

python3-jpype recommends no packages.

python3-jpype suggests no packages.

-- no debconf information

-- 
Tomáš "liskin" ("Pivník") Janoušek, https://lisk.in/

--- End Message ---
--- Begin Message ---
Source: python-jpype
Source-Version: 1.6.0-1
Done: Colin Watson <[email protected]>

We believe that the bug you reported is fixed in the latest version of
python-jpype, 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.
Colin Watson <[email protected]> (supplier of updated python-jpype 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: Wed, 03 Sep 2025 20:49:17 +0100
Source: python-jpype
Architecture: source
Version: 1.6.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team <[email protected]>
Changed-By: Colin Watson <[email protected]>
Closes: 1017761 1035211
Changes:
 python-jpype (1.6.0-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream release.
   * Use dh-sequence-python3 and dh-sequence-javahelper.
   * Use pybuild-plugin-pyproject.
   * Simplify some debhelper overrides.
   * Run most tests during build.
   * Look for system-installed org.jpype.jar (closes: #1017761).
   * Enable autopkgtest-pkg-pybuild (closes: #1035211).
Checksums-Sha1:
 62f28dd25ed52631fa357292300d2137035a9179 2284 python-jpype_1.6.0-1.dsc
 52a32d738009651fc9dcc0569a5ece8d0fa15de4 801839 python-jpype_1.6.0.orig.tar.gz
 15f4305a22da3eb93a242baa0743a77e7416209b 4944 
python-jpype_1.6.0-1.debian.tar.xz
Checksums-Sha256:
 90f651af8138aa078eff87fc26aff218c029ac8bcf65af7d3321358a52e65e9a 2284 
python-jpype_1.6.0-1.dsc
 01673112fed9c8a16b33fcd87a8e4b116b55c4bfaf116ae8a0b2b68b496e0c26 801839 
python-jpype_1.6.0.orig.tar.gz
 7471ed19126861ba4bd7b92e6907e6eb997b8b0bdf1a00e63c894cee89518b46 4944 
python-jpype_1.6.0-1.debian.tar.xz
Files:
 bb1145057fced5bdb8d9826b84e07f25 2284 python optional python-jpype_1.6.0-1.dsc
 4039eb4a910ce866bc7e7ca0012a7d2f 801839 python optional 
python-jpype_1.6.0.orig.tar.gz
 8f9096473432e4ff5be8c1879b15deb5 4944 python optional 
python-jpype_1.6.0-1.debian.tar.xz

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

iQIzBAEBCgAdFiEErApP8SYRtvzPAcEROTWH2X2GUAsFAmi4nAwACgkQOTWH2X2G
UAvOUA/+MOzfTIG8a8Oa7FafkdYYZXUZnD/cUjNEc7KadU65gWTsBrAiZfNVO9Jf
Jq3BHa2fNOudsc5UNMH1TxBB1TEwIxT6TWGirCbSdzTNlN8Xc5PxA3bqIPK0rSaD
wiCD+IKEZSK/wLPnJ7Z0YmYo/NRv3Jn6lcDeq/DD/JLW0+zuJim1ClVOKHKq9EHI
9PojkSnq7dx8j2YAAtPnrS66m54cQgphADSIJveHCaeB2ttffNWn7/1W5ehZZutB
7V7K7sSn1BczjXNSyV0ZNB/L5II+jsNJvSbJ0dB4EDe6cHQrIEg+ixTJSlzD0TCp
wRSYzaQj73KdiyvS1RKzuevX/FCG9jlZtO2zyqXlBYf5kteE85BQvisA56/Bancf
uRcdyyH/4qGIoMnNWr+/y23+ihqeSHz0c4f/T4EIk7Z+VZBB63OgjaFZjuIpC2a+
atI0mDuMGO8fKhn1sDe0TkvgwzyA2Ix98GYeD6fhsW6ztvNDGxRoy+3qLy4ey/QK
tzCZMjbawAphnF1rrBBe8vaE2uaR01wIbfuvFCQWPpLcPbYvNEAR17kwvVK+tCeK
S+tpsapZ5iXpCb/exAIwgfWkqVp8IHGs8lusbilvHnGBdbFKHbsUyIkYyJCt9UpG
r2+I9MiHt3WC4h3H64s1gp3XeBul5D+ox5msqKYt1He2T1048kM=
=wwVG
-----END PGP SIGNATURE-----

Attachment: pgpK9E_X0qX3d.pgp
Description: PGP signature


--- End Message ---

Reply via email to