Bug#1034824: tomcat9 should not be released with Bookworm

[Timo Aaltonen]

Timo Aaltonen kirjoitti 16.5.2023 klo 10.12:
> Markus Koschany kirjoitti 13.5.2023 klo 23.38:
>> Hi Salvatore,
>>
>> adding Timo Aaltonen, maintainer of dogtag-pki and tomcatjss, to CC
>>
>> Am Samstag, dem 13.05.2023 um 20:50 +0200 schrieb Salvatore Bonaccorso:
>>> Hi Markus,
>>>
>>> On Sat, May 13, 2023 at 06:27:49PM +0200, Markus Koschany wrote:
>>>> I have just pushed the necessary changes to our Git repository.
>>>>
>>>> https://salsa.debian.org/java-team/tomcat9/-/commit/adbd0b0711de66b67278b10e258c47c805e9b993
>>>
>>> Do we need to have done more here? When Paul asked on #debian-release
>>> I noted that pki-server depends on tomcat9-user, so reducing
>>> libtomcat9-java only would now cause a broken dpeends for pki-server:
>>>
>>> $ dak rm --suite=bookworm -n -R -b tomcat9-user
>>> Will remove the following packages from bookworm:
>>>
>>> tomcat9-user |   9.0.70-1 | all
>>
>> We could simply replace tomcat9-user with tomcat10-user because it 
>> only ships a
>> script to create a standalone tomcat instance. We have to do
>> s/tomcat9/tomcat10/ in some debian service files as well.
>>
>> The question is: If we ship libtomcat9-java in Bookworm and change the
>> dependency from tomcat9-user to tomcat10-user, will a web application 
>> like
>> dogtag-pki, which is designed for Tomcat 9, continue to work with 
>> Tomcat 10? I
>> don't know yet and maybe Timo can chime in here.
> 
> I don't know, dogtag uses the skel files from tomcat9-user, but I diffed 
> them between tomcat9 and 10 and couldn't see why it would regress.

Had a closer look at dogtag, and it's launching the tomcat instance from 
CATALINA_HOME, so it's a one-way ticket to migrate an installed instance 
to use tomcat10 in the configuration, so I don't think moving to 
tomcat10-user would fly..


-- 
t