Bug#1034824: tomcat9 should not be released with Bookworm

[Paul Gevers]

Hi Markus,

On Tue, 25 Apr 2023 16:04:09 +0200 Markus Koschany <apo at debian.org> wrote:
> We can only support one major Tomcat version per release. Tomcat9 has
> been part of Buster and Bullseye already and is superseded by Tomcat
> 10 in Bookworm. I wanted to wait with the removal request until the
> issues in [resteasy3.0] and [tomcatjss] have been resolved but to make
> it more obvious I am filing this bug report now.

Release Team member here. I'll note that I'm not impressed by the 
communication and timing of this bug. We're in Full Freeze for bookworm. 
This is no time for transitions, let alone for *uncoordinated* ones.

You should have raised the issue earlier and brought it to the release 
team. tomcat9 and tomcat10 are both key packages so neither can easily 
be removed.

 From a quick look at the key packages:

It seems you didn't follow up (86 days) on libcommons-dbcp-java which 
can't migrate to bookworm because it would make libbiojava-java-doc 
uninstallable (no fix there, no bug report filed).

src:tiles also build-depends on libtomcat9-java, with no bug filed for 
the migration to tomcat10 *and* it having it's own FTBFS bug. (It's key 
because of src:libspring-java)

On IRC carnil and jmm_ suggested that src:tomcat9 could be left in 
bookworm but have it's server component stripped. Would that help the 
situation?

Everything in this transition would still need an unblock by the release 
team, as we're now very close to the hard freeze (24 May) and nearly 
ready to release.

Paul
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 495 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-java-maintainers/attachments/20230511/99d43d79/attachment.sig>