<div dir="ltr"><div class="gmail_default" style="font-size:small">I think getting tomcat 10 into unstable so it is in a path to eventually making into testing and then stable has become a higher priority now that tomcat 10 is required when using webapps developed using the latest Spring framework version (<a href="https://github.com/spring-projects/spring-framework/wiki/Upgrading-to-Spring-Framework-6.x" target="_blank">https://github.com/spring-projects/spring-framework/wiki/Upgrading-to-Spring-Framework-6.x</a>)</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">Thus IMHO we should resolve this issue by adding the Breaks+Replaces to libtomcat10-java and give up co-instalability. Of course we should immediately open a feature request to get co-instalability back, but that would not stop the package from going into unstable and, after bookworm is released, testing.<br></div></div>