Debian Patches

Status for jline4/4.0.14+ds2-1

Patch	Description	Author	Forwarded	Bugs	Origin	Last update
0001-jni-library-in-jline4-subdirectory.patch	Look for the JNI library in a jline4 subdirectory first JLine 3 and JLine 4 both name their JNI library libjlinenative.so. So that libjline3-jni and libjline4-jni can be installed together, libjline4-jni installs it as /usr/lib/<triplet>/jni/jline4/libjlinenative.so. Before the plain java.library.path lookup, try the jline4 subdirectory of every java.library.path entry, so that JLine 4 loads its own build of the library rather than the one of libjline3-jni.	Juan Manuel Méndez Rey <juan.mendezr@proton.me>	not-needed			2026-10-02
0002-pom-version.patch	Give the POMs of the packaged modules a literal version Upstream computes the version at build time from git with the nisse Maven extension, and the POMs say ${nisse.jgit.dynamicVersion}. The extension is not used in Debian. debian/rules defines that property for the build, but the POMs installed in /usr/share/maven-repo need the real version, so the root POM and the POMs of the modules this package builds (native, terminal, terminal-jni, reader) get it here. Refresh on every new upstream version.	Juan Manuel Méndez Rey <juan.mendezr@proton.me>	not-needed			2026-10-02