Bug#965006:

[Jorge Moraleda]

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 (
https://github.com/spring-projects/spring-framework/wiki/Upgrading-to-Spring-Framework-6.x
)

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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-java-maintainers/attachments/20230113/b178bd0e/attachment.htm>