Path: csiph.com!1.us.feeder.erje.net!3.us.feeder.erje.net!3.eu.feeder.erje.net!feeder.erje.net!news2.arglkargh.de!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod From: Emmanuel Bourg Newsgroups: linux.debian.maint.java Subject: Tomcat 10 packaging Date: Wed, 28 Sep 2022 18:10:01 +0200 Message-ID: X-Original-To: Debian Java X-Mailbox-Line: From debian-java-request@lists.debian.org Wed Sep 28 16:04:41 2022 Old-Return-Path: X-Amavis-Spam-Status: No, score=-7.701 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -5.5 X-Greylist: delayed 534 seconds by postgrey-1.36 at bendel; Wed, 28 Sep 2022 16:04:22 UTC Authentication-Results: apache.org; auth=none MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.13.1 Content-Language: en-US Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Mailing-List: archive/latest/23084 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/2ec106f2-3007-4b56-7727-ab009eef4756@apache.org Approved: robomod@news.nic.it Lines: 32 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Wed, 28 Sep 2022 17:53:57 +0200 X-Original-Message-ID: <2ec106f2-3007-4b56-7727-ab009eef4756@apache.org> Xref: csiph.com linux.debian.maint.java:12444 Hi all, For Debian Bookworm I'd like to replace Tomcat 9 with Tomcat 10. But this time instead of introducing a "tomcat10" package, I wonder if we could instead create a version-less "tomcat" package and keep it for the next major releases. Pros: - no need to create a new package, replacing tomcat with tomcat everywhere, and then wait for the NEW queue - unique packaging repository - no more transition, replacing the libtomcat-java dependency with libtomcat-java everywhere (currently about 15 packages) - no need to install tomcat and transfer /etc/tomcat to /etc/tomcat when upgrading Debian - the log files and the deployed web applications also remain at the same place Cons: - the unique repository will probably have multiple upstream branches when Tomcat upgrades are uploaded to oldstable as part of the LTS, this may be tricky with gbp - if the new configuration files are incompatible with the previous format, upgrading Debian may break the Tomcat instance. Either it no longer starts, or some configuration elements or features no longer work. With separate packages, the system upgrade is unlikely to break Tomcat, but the user may forget to upgrade it and will keep an unsupported instance that is no longer receiving security updates. What do you think? Emmanuel Bourg