On Fri, 11 Nov 2022, Emmanuel Bourg wrote: > default-jre-headless | java11-runtime-headless > > Let's assume this is changed in bookworm to: > > default-jre-headless | java-runtime-headless (>= 11) > > Considering a tomcat9 user upgrading from bullseye to bookworm, there are two > cases: > > 1. the default JRE was used on bullseye, default-jre-headless and > openjdk-11-jre were already installed. During the upgrade, openjdk-17-jre is > pulled (required by default-jre), openjdk-11-jre remains (but could be removed > manually), and tomcat9 expects java-runtime-headless (>= 11) which is > satisfied by both default-jre-headless and openjdk-17-jre-headless. Tomcat > will run with OpenJDK 17 and all is fine.
3. openjdk-11-jre-headless was used in bullseye (most people I know do this to avoid the needless metapackage), the user will end up with both because the Provides on java-runtime-headless in bullseye was unversioned but maybe they don’t (worse if the package is backported). It’s worse for sid users, especially for rare cases. gn8, //mirabilos -- Infrastrukturexperte • tarent solutions GmbH Am Dickobskreuz 10, D-53121 Bonn • http://www.tarent.de/ Telephon +49 228 54881-393 • Fax: +49 228 54881-235 HRB AG Bonn 5168 • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg **************************************************** /⁀\ The UTF-8 Ribbon ╲ ╱ Campaign against Mit dem tarent-Newsletter nichts mehr verpassen: ╳ HTML eMail! Also, https://www.tarent.de/newsletter ╱ ╲ header encryption! ****************************************************
