- Package:
- src:tomcatjss
- Source:
- src:tomcatjss
- Submitter:
- Emmanuel Bourg
- Date:
- 2025-04-22 17:09:07 UTC
- Severity:
- normal
libtomcatjss-java uses libtomcat9-java but this package is about to be removed. libtomcat10-java should be used instead.
Upstream doesn't support tomcat10 yet, and tomcatjss fails to build with it.
Control: severity -1 serious Unfortunately we can only support one Tomcat version per release. We should either migrate to tomcat10 or maybe it is possible to embed some of the required tomcat9 classes in your source package as a workaround provided the changes are rather small and the security impact is negligible. Regards, Markus
Markus Koschany kirjoitti 23.3.2023 klo 19.00: Right, but that's for bookworm+1? By that time I'm sure jss/tomcatjss/dogtag have gained upstream support for tomcat10.
Am Freitag, dem 24.03.2023 um 09:21 +0200 schrieb Timo Aaltonen: We are targeting Bookworm. We had Tomcat 8 in Stretch and Tomcat 9 in Buster and Bullseye already. Tomcat 10 also targets Java 11 and later while Tomcat 9 was intended for Java 8 and later. We ship OpenJDK 17 in Bookworm. resteasy3.0 and tomcatjss are the only packages apart from i2p that still depend on libtomcat9-java.
Markus Koschany kirjoitti 24.3.2023 klo 15.35: Nice, so you expect them to migrate after bookworm is already frozen?
Am Sonntag, dem 26.03.2023 um 12:15 +0300 schrieb Timo Aaltonen: Targeted fixes are still allowed. Including required tomcat9 classes in your package may be a solution too. If you can find an agreement with the security and release team, then even shipping libtomcat9-java might be possible. But then your packages will not receive any security support.
I've added the release team to Cc, since trying to force a tomcat 9 -> 10 transition after the start of the transition freeze and after the start of the soft freeze sounds forbidden to me. cu Adrian
Does that mean the two bugs (in tomcat9 and tomcatjss) should be tagged "trixie sid" to no longer affect and bookworm will ship with two versions of tomcat, or what else is now supposed to happen? cu Adrian
Dear submitter, as the package tomcatjss has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1100392 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmaster@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)