[request-tracker-maintainers] Bug#1026669: Bug#1026669: request-tracker5: FTBFS: can't locate java: No such file or directory

[Niko Tyni]

Control: clone -1 -2
Control: retitle -2 jexec: can't locate java: No such file or directory
Control: reassign -2 openjdk-17-jre-headless 17.0.5+8-2

On Wed, Jan 18, 2023 at 04:10:02AM +0100, Ángel wrote:
> The error here is that ./debian/build-final-ckeditor.sh fails with
> « can't locate java: No such file or directory »
> 
> This script is actually calling ckbuilder ( jexec /usr/bin/ckbuilder --
> build ... )
> 
> However, the package correctly lists ckbuilder as a build-dep, and
> ckbuilder itself depends on java ( default-jre | java{7..11}-runtime)

> > update-alternatives: using /usr/lib/jvm/java-17-openjdk-
> > amd64/lib/jexec to provide /usr/bin/jexec (jexec) in auto mode

Yeah, it looks to me like jexec from openjdk-17-jre-headless
is just broken on sid?

% jexec
can't locate java: No such file or directory

% ls -l /usr/bin/jexec /etc/alternatives/jexec /usr/lib/jvm/java-17-openjdk-amd64/lib/jexec
lrwxrwxrwx 1 root root    44 Oct 19 14:23 /etc/alternatives/jexec -> /usr/lib/jvm/java-17-openjdk-amd64/lib/jexec
lrwxrwxrwx 1 root root    23 Oct 19 14:23 /usr/bin/jexec -> /etc/alternatives/jexec
-rwxr-xr-x 1 root root 14416 Oct 19 14:23 /usr/lib/jvm/java-17-openjdk-amd64/lib/jexec

% ls -l /usr/bin/java /etc/alternatives/java  /usr/lib/jvm/java-17-openjdk-amd64/bin/java
lrwxrwxrwx 1 root root    43 Oct 19 14:23 /etc/alternatives/java -> /usr/lib/jvm/java-17-openjdk-amd64/bin/java
lrwxrwxrwx 1 root root    22 Oct 19 14:23 /usr/bin/java -> /etc/alternatives/java
-rwxr-xr-x 1 root root 14424 Oct 19 14:23 /usr/lib/jvm/java-17-openjdk-amd64/bin/java

% java --version
openjdk 17.0.5 2022-10-18
OpenJDK Runtime Environment (build 17.0.5+8-Debian-2)
OpenJDK 64-Bit Server VM (build 17.0.5+8-Debian-2, mixed mode, sharing)

I'm cloning a separate bug about this.

Not sure why jexec is used here though. Just running /usr/bin/ckbuilder
works for me (but the request-tracker5 build fails later, presumably
due to a different bug.)

-- 
Niko Tyni   ntyni at debian.org