Bug#1114028: Regression of #1020948 introduced in bullseye-security (looking up for OpenJDK 17)
Santiago Ruano Rincón
santiagorr at riseup.net
Thu Sep 11 17:29:07 BST 2025
El 11/09/25 a las 09:40, Santiago Ruano Rincón escribió:
...
> Other than re-adding 17 to the exec script, I hope this dep-8 test could
> help to identify this regression in the future:
>
> diff --git a/debian/tests/control b/debian/tests/control
> new file mode 100644
> index 00000000..70ce2f08
> --- /dev/null
> +++ b/debian/tests/control
> @@ -0,0 +1,2 @@
> +Tests: detect-openjdk-17
> +Depends: @, openjdk-17-jre
> diff --git a/debian/tests/detect-openjdk-17 b/debian/tests/detect-openjdk-17
> new file mode 100644
> index 00000000..5fd57d3d
> --- /dev/null
> +++ b/debian/tests/detect-openjdk-17
> @@ -0,0 +1,3 @@
> +#!/bin/sh
> +
> +sh /usr/libexec/tomcat9/tomcat-locate-java.sh
>
> Currently testing in my tomcat9's fork. I'll report if this doesn't work
> as expected.
Well, I am reporting despite it seems to work:
https://salsa.debian.org/santiago/tomcat9/-/jobs/8259632
For being able to trigger a pipeline in salsa, you need to enable the
CI, configuring it the bullseye's recipe.
And uploading via debusine.d.n would also trigger the autopkgtest tasks.
HTH,
-- S
More information about the pkg-java-maintainers
mailing list